Travers Carter a écrit :
> On Thu, 20 Aug 2009 00:45:36 +0300, Noor
> <>
> wrote:
>> And while you're at it, I'll through in another question: How does
>> eAccelerator/FastCGI manage the shared memory segments? According to
>> eAccelerator's homepage, it'll share such segments when the spawning
>> process is shared. In the case of FastCGI (mod_fcgid), *who* is the
>> spawning process? And this spawning process, how many cgi-php
>> processes it'll spawn? (which if I understand correctly, such cgi-php
>> processes would share eAccelerator's cached scripts as they've got one
>> "father").
> As I understand it in FastCGI mode a php process will launch a number
> of children equal to the value of the PHP_FCGI_CHILDREN environment
> variable, I believe that this is the spawning process referred to in
> the eAccelerator docs, meaning that the shared memory segment would
> be shared by those PHP_FCGI_CHILDREN processes.
> But mod_fcgid (unlike mod_fastcgi) assumes that each process it starts
> directly can only handle a single concurrent request so
> PHP_FCGI_CHILDREN should be set to 0, meaning that no children will be
> launched and the shared memory segment will only be used by a single
> php process.
PHP will shutdown the process after 500 request, so if you don't use 
opcode cache (eaccelerator/xcache/apc) will be lost.
For this type of setup I generally set PHP_FCGI_CHILDREN to 1 and 
increase the
"ProcessLifeTime" fastcgi parameter to 86400 seconds instead of 3600.


Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.
Mod-fcgid-users mailing list

Reply via email to