Hi again,
On Thu, 21 Mar 2002, David Brown wrote:
> OK, I have it working now.
Guess I shold read ALL my mail before replying to any of it...
73,
Ged.
Hi there,
On Thu, 21 Mar 2002, Perrin Harkins wrote:
> When you call the script, do you get segfaults in the error log?
Coming into this thread a little late, so sorry if you already said,
what version of Perl are you using? I had problems with Devel::Dprof
and dprofpp on 5.7.1 which were fixe
: "Perrin Harkins" <[EMAIL PROTECTED]>
To: "David Brown" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, March 21, 2002 7:07 PM
Subject: Re: Subroutines taking time to return..
> David Brown wrote:
> > All good and well I thought.. But
David Brown wrote:
> All good and well I thought.. But erm.. nothing is being created in the
> dprof directory in the server-root.
When you call the script, do you get segfaults in the error log?
Make sure that you do the DProf stuff, including Apache::DB->init(),
before you load any of your ot
David Brown wrote:
> Thankyou, but I have read the documentation.
>
> Nothing gets written to a rootdir/dprof directory, not even an empty file
> when the scripts are run.
sorry, you should have told this :0)
Could be write permissions?
Can you profile a normal perl script?
>>You aren't doing
Thankyou, but I have read the documentation.
Nothing gets written to a rootdir/dprof directory, not even an empty file
when the scripts are run.
> You aren't doing it wrong. Next step is to run the script and usually it
> helps to read the docs :)
David Brown wrote:
> Great feedback, many thanks. But as always, one problem becomes another !
>
> I've compiled + installed Apache-DB
> I've compiled + installed DProf-19990108
>
> I've added this to my httpd.conf:
>
> PerlModule Apache::DProf
>
> I've added this to my modperl.conf (called b
Great feedback, many thanks. But as always, one problem becomes another !
I've compiled + installed Apache-DB
I've compiled + installed DProf-19990108
I've added this to my httpd.conf:
PerlModule Apache::DProf
I've added this to my modperl.conf (called by httpd.conf):
use Apache::DProf;
use
Perrin Harkins wrote:
>>You cannot reliably measure CPU clocks with wallclock on the
>>multi-processor machine, unless you are running on Dos :)
>>
>
> Even so, wall time is what most people actually care about, and it's
> fine to use if you're the only one doing work on that machine.
Yes, for c
> You cannot reliably measure CPU clocks with wallclock on the
> multi-processor machine, unless you are running on Dos :)
Even so, wall time is what most people actually care about, and it's
fine to use if you're the only one doing work on that machine.
> Also search the archives, about a year
David Brown wrote:
> I've been profiling my MySQL driven Mod_Perl website by adding debug
> messages throughout the code which relays what time has elapsed since the
> script was invoked (using Time::HiRes)
>
> Now the script is pretty whizzy, serving up complete pages in circa 0.010
> seconds.
>
Hi there,
On Wed, 20 Mar 2002, David Brown wrote:
> I've been profiling my MySQL driven Mod_Perl website
[snip]
> (using Time::HiRes)
[snip]
> I expected all the complicated DB access stuff to make up the time
MySQL is pretty quick. :)
> instead it seems to be consuming 0.005 in returning fro
Have you tried using Apache::DProf? Using this is a lot easier than
trying to add tons of debug messages. If you haven't used it or the
regular DProf, it does what your doing automatically. It generates a
file of data that you run 'dprofpp' on and you can get a list of the top
10 or so most t
13 matches
Mail list logo
