[Catalyst] DProf

[Peter Edwards]

Have you tried using the Apache stats?

In /etc/httpd/conf/httpd.conf

  ExtendedStatus On
  <Location /server-status>
    SetHandler server-status
    Order deny,allow
    Deny from all
    Allow from .your.domain
  </Location>
  <Location /server-info>
    SetHandler server-info
    Order deny,allow
    Deny from all
    Allow from .your.domain
  </Location>

In /etc/httpd/conf.d/perl.conf (or similar)

  <Location /perl-status>
    SetHandler perl-script
    PerlResponseHandler Apache2::Status
    Order deny,allow
    Deny from all
    Allow from .your.domain
  </Location>


Then browse to get more information
http://your.server/server-status 
At a peak busy time look for Apache children with a 'W' in the 'M' column.
These are busy working and show you what is tying up your server.

Also
http://your.server/server-info 
Apache config
http://your.server/perl-status 
Perl config

Depending on what's using your Apache time up, you may get better
performance by compiling a lightweight frontend Apache that serves static
files and proxies application requests to a backend Apache compiled with
mod_perl.

Regards, Peter
Dragonstaff Limited  http://www.dragonstaff.com   Business IT Consultancy

-----Original Message-----

> I've tried to put ab to run more concurent connections in order to check
how 
> occupied will be the processor