I've no idea what stability impact the profiler would have. It does impact CPU
usage and memory consumption, it also generates potentially very large log
files if it's running for any significant amount of time. You also have to
shut the server down to finalise the profile logs (otherwise they
Hi malcolm,
Malcolm J Harwood wrote:
On Thursday 14 October 2004 04:23 am, Victor Tsang wrote:
We use mod_perl heavily here, and lately I notice some apache
children for some reason chew up large amount of cpu (indeed all cpu).
Using apache's server-status i can tell it is one of the new script
On Thursday 14 October 2004 10:49 pm, victor wrote:
> Hi malcolm,
> >This might be stating the obvious, but have you run it under a profiler? (
> >Devel::Profiler::Apache is what I've been using). If it's a problem with
> > the actual perl script, that should give you a good idea what part of the
On Thursday 14 October 2004 04:23 am, Victor Tsang wrote:
> We use mod_perl heavily here, and lately I notice some apache
> children for some reason chew up large amount of cpu (indeed all cpu).
> Using apache's server-status i can tell it is one of the new script
> we have deployed that caused
Hello everyone,
This could be a bit off topic, please kindly forgive me if it is so,
I am seeking for tips on debugging perl script that is running under
mod_perl.
We use mod_perl heavily here, and lately I notice some apache
children for some reason chew up large amount of cpu (indeed all cp
