(I work with
dws)
>
The first is measuring CPU time in an application that is I/O bound.
*nod* Our default quickie-profiling command defaults to wall-time instead of cpu-time:
perlp is a function
perlp ()
{
perl -d:DProf "$@";
dprofpp -r -O 30 >"${1}.prof";
cat "${1}.prof"
}
>
try[ing] to profile mod_perl apps but load their code before initializing the debugger.
We can't even profile our code which gets run under mod_perl in a non-mod_perl context (profiling it while under execution by one of our unit tests, for instance, or while driven by a targeted one-off script).