in reply to Profiling forking code?
You could replace the "real" method/sub names with some prefixed form, and then use AUTOLOAD to generate stubs that log what's being called with high-res start time, call prefixed form, then log end time. You should probably have that AUTOLOAD stub log to per-pid logfiles, to avoid having to lock things.
If your modules are "regular" enough, you could even write a perl script to instrument your modules :)
This is pretty well what a profiler would do for you, but since you're forking, I think you might have to do it for yourself...
Of course, this involves modifying the module sources. :( But if you're not profiling, you could have the AUTOLOAD sub alias *outerform=&innerform.
--
Mike
|
|---|