Profiling under mod

aufflick has asked for the wisdom of the Perl Monks concerning the following question:

Hi esteemed Apache::Monks,

I am trying to profile a large app made from a combination of a large number of perl modules and a thin layer of mason components.

I have tried starting apache with -C 'PerlModule Apache::DProf 'or -C 'PerlModule Devel::Profiler::Apache' — I get no errors, but I also get no profile files created.

I know that's not a lot of information, but with no errors and no output I'm stumped for what to look for! Has anyone had to solve this before? I suppose I can debug the runnig process and see if the handlers are registered etc. Could my problem be that the handler is registered after Mason? I have tried using -C and -c for different startup order to no avail.

gah.

Mark.

Comment on Profiling under mod_perl

Replies are listed 'Best First'.
Re: Profiling under mod_perl by perrin (Chancellor) on Feb 16, 2005 at 03:06 UTC
I've never heard of anyone trying to do this with -C before. Just add it to your config file. I'm not sure it will work ouutside of a specific Location block. There is some documentation here.	[reply]
Re^2: Profiling under mod_perl by aufflick (Deacon) on Feb 21, 2005 at 23:52 UTC
Nope - tried that. No dice... I suspect that my mason handler is connecting to mod_perl higher (or earlier - depending on your mental model) and thus is being excluded as part of the startup.	[reply]
Re^3: Profiling under mod_perl by perrin (Chancellor) on Feb 22, 2005 at 00:09 UTC
Put this in your httpd.conf before anything else that loads a perl module: `<Perl> require Apache::DB; Apache::DB->init; </Perl>` [download]	[reply] [d/l]
Re^4: Profiling under mod_perl by aufflick (Deacon) on Feb 22, 2005 at 00:17 UTC
Re^5: Profiling under mod_perl by perrin (Chancellor) on Feb 22, 2005 at 00:29 UTC
Some notes below your chosen depth have not been shown here