I have this in m php-fcgid.conf
AddHandler fcgid-script .fcgi .php # Where to look for the php.ini file? DefaultInitEnv PHPRC "/etc/php5/cgi" # Maximum requests a process handles before it is terminated MaxRequestsPerProcess 1000 # Maximum number of PHP processes MaxProcessCount 10 # Number of seconds of idle time before a process is terminated IPCCommTimeout 300 IdleTimeout 240 #Or use this if you use the file above FCGIWrapper /usr/bin/php-cgi .php ServerLimit 500 StartServers 3 MinSpareThreads 3 MaxSpareThreads 10 ThreadsPerChild 10 MaxClients 300 MaxRequestsPerChild 1000 From: [email protected] [mailto:[email protected]] On Behalf Of nick tailor Sent: Tuesday, February 26, 2013 7:28 PM To: Stephen Strickland Cc: [email protected] Subject: Re: Varnish with mod prefork vs mpm worker with mod-fcgid I believe it has to do with the new processes being spawned. You might need to tweak the fastCGI processes to allow more request per process in one of your confs MaxRequestsPerProcess 1000 MaxProcessCount 5 IPCCommTimeout 600 IdleTimeout 600 Hope that helps Cheers Nick Tailor On Tue, Feb 26, 2013 at 3:30 PM, Stephen Strickland <[email protected]> wrote: I running a site with Drupal 7 and with apache2 installed initially I was using mod prefork, I was getting varnish hit rates at least high 80's or middle 90s. I changed to mpm worker with mod_fcgid and now I am now getting an average of 25%. Anyone out there know of anything that could be causing this? _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc _____ No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.2899 / Virus Database: 2641/6135 - Release Date: 02/26/13
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
