in reply to Cache::FileCache, CPU utilization, and bottlenecks ....

One of the first things you should do is profile your handler and look at the results to see the resource distribution within your request.
  • Comment on Re: Cache::FileCache, CPU utilization, and bottlenecks ....

Replies are listed 'Best First'.
Re^2: Cache::FileCache, CPU utilization, and bottlenecks ....
by geektron (Curate) on Jan 10, 2005 at 23:46 UTC
    well, profiling is now on tomorrow's to-do list.
Re^2: Cache::FileCache, CPU utilization, and bottlenecks ....
by geektron (Curate) on Jan 11, 2005 at 06:05 UTC
    well, tomorrow came early (because it seemed like an interesting thing to do), but i must be missing something.

    the perldoc indicates that all that's needed is an inclusion of this line:

    #in httpd.conf PerlModule Apache::DProf
    i've added that in the VirtualHost container, but i don't see *any* dprof directories, either in the server root for the VH, or in the log dirs .. <p< i've run a  find / -type d -name dprof -print and it turned up nothing ....

    so, does this need to be in the main httpd.conf, and i'm going to have to try and isolate the pids for one VH, or is there something i'm missing, like making the handler a subclass of Apache::DProf ?

      There's a chapter in the Practical mod_perl book by Stas Bekman which has an overview of profiling and includes a section on Apache::DProf , this might be able to help you out.

      From other posts on this thread though it might just be worth it to go with Cache::Memcached, which should provide a big speedup.