On Nov 12, 2007 3:25 PM, E R <[EMAIL PROTECTED]> wrote:
> 1. a call to $profile->mark(...) will emit a special record to the log file
> 2. on server start up, spawn a single process to monitor the log file
> and collect profile records
> 3. have the monitoring process listen on a socket for request
On Nov 12, 2007 11:25 AM, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> i'm just tossing this idea out...
Thanks for the ideas. The main issue I'm trying to find a good
solution for is the collection of the profiling info from all the
child processes because occasionally I want to poll the stats i
On Nov 12, 2007 10:59 AM, E R <[EMAIL PROTECTED]> wrote:
> 1. I don't want to profile every single subroutine. In fact, I want to
> profile only specific locations within my code, and a subroutine may
> have more than one profiling location.
You can control which packages are profiled. Check the
i'm just tossing this idea out...
1) have a profiler package that handles all the logging, etc - and
uses a constant
package MyApp:::Profiler;
use constant DO_PROFILE=> 1;
sub profile {
my ( $marker )= @_ ;
#log;
}
1;
2)
On Nov 12, 2007 9:51 AM, Geoffrey Young <[EMAIL PROTECTED]> wrote:
> this should help:
>
> http://search.cpan.org/dist/Devel-Profiler/lib/Devel/Profiler/Apache.pm
The two problems I see with this package are:
1. I don't want to profile every single subroutine. In fact, I want to
profile only spec
E R wrote:
> Hi,
>
> I have the need for a simple profiling capability for mod_perl applications.
> At a few (< 50) points in my code I want to call something like:
>
> $profiler->mark("some identifier");
>
> and increment the counter for "some identifier". Later I want to be able to
> get
>
