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, l
On Mon, 15 Aug 2005 11:42:52 -0400
Perrin Harkins <[EMAIL PROTECTED]> wrote:
> Frank Wiles wrote:
> > Give Apache::SmallProf a try. Where Apache::DProf shows you the
> > subroutine calls, SmallProf will show you a profile on a line by
> > line basis. This should help you zero in on what is
Frank Wiles wrote:
Give Apache::SmallProf a try. Where Apache::DProf shows you the
subroutine calls, SmallProf will show you a profile on a line by line
basis. This should help you zero in on what is causing the slowness.
I'd say just the opposite in most cases. Usually you want to see
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?
On Mon, 15 Aug 2005 14:59:00 +1000
"Badai Aqrandista" <[EMAIL PROTECTED]> 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
n't really accurate. How do I make it to show the
statistics of the subroutines called from the handler?
Thank you...
---
Badai Aqrandista
Cheepy (?)
From: "Philip M. Gollucci" <[EMAIL PROTECTED]>
To: Badai Aqrandista <[EMAIL PROTECTED]>
CC: modperl@perl.apache.o
(I only try to improve the speed of the code, so the use of proxy
shouldn't be relevant here - I think, I could be wrong).
You might try using
Apache::DProf
and/or
Apache::SmallProf
available here to see where your code is spending its time
http://search.cpan.org/~fwiles/Apache-DB
