Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

Re: Profiling woes

by stiller (Friar)
on Apr 09, 2008 at 11:29 UTC ( #679206=note: print w/ replies, xml ) Need Help??


in reply to Profiling woes

I'm not exactly wise, but anyway: what makes your application slow is probably tightly related to the cause of profilers deaths. I'd try to narrow the problem down as much as possible, to isolate the module / set of modules that cause trouble. Try commenting out, e.g. with POD. Is there some heavy lifting in an inner loop somewhere?

Do you have tests for the project spesific modules? They should probably be prime suspects... If you make simple tests to check their sanity, you can also to profile these tests in isolation.

Good luck!


Comment on Re: Profiling woes
Re^2: Profiling woes
by apl (Monsignor) on Apr 09, 2008 at 11:53 UTC
    try to narrow the problem down as much as possible
    Exactly. If it's a CGI that uses DBI, create two test programs, one that only uses the CGI functionality, the other that only performs the DBI functionality. Find which one runs slow. Break that test program down...
      I actually only mentioned CGI because of eventual interaction with the profiling environment.
      But the script is really dependant of getting its data from the database, hard to do without (ok I could do without if I had some stub objects and data, but I don't for now).
      That's why I really thought I had a good approach with the profiling (for once).
Re^2: Profiling woes
by perrin (Chancellor) on Apr 09, 2008 at 12:57 UTC
    what makes your application slow is probably tightly related to the cause of profilers deaths
    Probably not, actually. The deaths are most likely caused by a bug in perl's debugging hooks. There's no reason to think that the part causing the crash is slow.
Re^2: Profiling woes
by goupilInside (Sexton) on Apr 09, 2008 at 15:33 UTC

    Well that's what I was trying to avoid thinking that profiling would give me a more elegant approach.

    What makes it more tedious is that some of the modules do have documentation and tests, and tend to have been used in various other programs. Some are more in the philosophy "write once", read never ....

    Thanks anyway

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://679206]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (14)
As of 2014-10-23 18:54 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    For retirement, I am banking on:










    Results (128 votes), past polls