On 28.2.2009, at 17:27, Olivier B. wrote:

> my first question was about that : it seems that fcgid will _never_  
> use
> this concurrent PHP instances. If there is 2 concurrent access, fcgid
> will spawn an other "group" of PHP to handle that, it will not use the
> first group of php instance which have idled children. So in this  
> groups
> of PHP, there is only one php child really used.
> If it is just to keep the opcode cache after PHP die (by default all  
> the
> 500 queries), well, just 1 fork in necessary.

Yes, well, my point was... if you care about shared memory, then  
constrain mod_fcgid to a single PHP process only, let the PHP process  
fork its own children and hope they will be able to process all  
requests before mod_fcgid considers the single process busy and you  
end up getting 503. If you do not care about shared memory, then leave  
out the PHP forks altogether (not setting PHP_FCGI_CHILDREN), and let  
mod_fcgid do its job. But it doesn't make much sense to intermix the  
two forking levels.


Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
Mod-fcgid-users mailing list

Reply via email to