Hello,

I'd appreciate some help here, as I've spent the better part of my
work day slamming my head against the wall with this one.

To give some background, I'm trying to benchmark a perl web
application running on Apache, Perl 5.8.9.  Naturally, I'm using the
Devel::NYTProf::Apache package for this.  In the simplest of setups,
when I only put "PerlModule Devel::NYTProf::Apache" in httpd.conf.  I
then run httdperf to slam my webserver, and I see plenty of files that
match the default format of /tmp/nytprof.$parent.out.$$.  This is fine
and dandy, since each of my apache processes spawns many workers, but
the problem I'm running into is that when I run nytperfhtml on any of
these, I'm experiencing a couple problems, one the line by line
profiling isn't working out, numerous lines are skipped and the
statement count is very off.  And secondly, I'm unable to see any of
the files that are being run via perl -e.

In an attempt to solve the above problem, I wanted to try out using
the settings optimize=0:use_db_sub=1.  So, I added "PerlSetEnv NYTPROF
optimize=0:use_db_sub=1" to httpd.conf.  I restart apache, slam my
webserver, but now, despite not supplying any output file location,
the files now are output to my current working directory (not /tmp/).
Furthermore, they no longer have their worker process IDs.  This is
bad, because the vast majority of the work is being done in these
worker threads, and these files seem to only contain the
initialization sequences.

Essentially what I'm trying to figure out is if there a way to specify
the worker process id within the file portion of the NYTPROF
environment variable.  I was hoping specifying the file such as
"PerlSetEnv NYTPROF optimize=0:use_db_sub=1:file=/nytprof/nytprof.
$parent.out.$$" would work, but that only literally places the dollar
signs in the file name.

So, if anyone knows how to solve the specifying the worker ID problem,
I'd most appreciate it.  If you have another solution for getting the
nytperfhtml report generation to include the perl -e files (outside of
upgrading perl, though I may wind up doing that), I'd much appreciate
it.

Thanks,

Brian

-- 
You've received this message because you are subscribed to
the Devel::NYTProf Development User group.

Group hosted at:  http://groups.google.com/group/develnytprof-dev
Project hosted at:  http://perl-devel-nytprof.googlecode.com
CPAN distribution:  http://search.cpan.org/dist/Devel-NYTProf

To post, email:  [email protected]
To unsubscribe, email:  [email protected]

Reply via email to