It can tell you all these things, you just need to massage it correctly, and know your app well enough to associate subroutine names with implementations. (you should read the man page for dprofpp as well, that's the DProf profile parser which allows you to interperet your trace files. For (potentially excessive) detail, use the -t option to get a compacted call tree. That combined with the summary statistics can give you a good feel for where time is being spent, and what the fow of the application is.
One note of caution: DProf exects your application to exit naturally. If this is a daemonizing app that is not suppsoed to exit, you may want to wrap it so that it can run for a set period of time and then exit. Otherwise you may have probles with your statistics. George Jason Frisvold wrote: >Thanks, I'm looking into it now... :) > >We were specifically wondering if there was something that could count >loops, count db calls, and related items like that ... It looks like >this profiler will tell you the time spent in subroutines, but not more >specifics? Of course, I need to do more reading on this ... looks like >it may do a lot more than meets the eye ... :) > >Friz > >On Mon, 2002-10-07 at 14:31, George Schlossnagle wrote: > >>perldoc Devel::DProf >> >>It's a very useful and functional profiler (IMHO). >> >>George >> >> >>Jason Frisvold wrote: >> >>>Does anyone know if there is a Perl Profiler (Open Source or Commercial) >>>that is in existance? Apparently my boss thinks this will magically fix >>>various issues... :) >>> >> >> -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
