Badai Aqrandista wrote:
I doubt the ApacheHandler::handler subroutine runs that long, because it
only shows the accumulated time used by other subroutines it calls. That
makes the profile isn't really accurate. How do I make it to show the
statistics of the subroutines called from the handler?
First, give dprofpp the flag that makes it sort by wall time, not by CPU
time. Otherwise, things that take most of the time in the average
program, like I/O, will appear to be very fast.
Second, make sure you initialize the debugger before loading any of the
code that you want to profile, like this:
<Perl>
require Apache::DB;
Apache::DB->init;
</Perl>
Any code that you compile (e.g. use from startup.pl) before this will
not get profiled at all.
- Perrin
