httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 48110] Doc of mod_fcgid: "PHP child process management" appears incorrect
Date Tue, 03 Nov 2009 15:49:29 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=48110

--- Comment #2 from HWS <strube@physik3.gwdg.de> 2009-11-03 07:49:28 UTC ---
Well, I think that the PHP child processes are simply irrelevant to mod_fcgid;
the  parent PHP is the only one seen and treated like a single PHP process. I
do not understand "if the PHP process created by mod_fcgid is idle or has an
idle child process because it has passed a current request to a child,
mod_fcgid still will not send another request to it." How can the parent PHP
process possibly be considered idle by mod_fcgid as long as one of its children
is still processing a request?
But you really make an important point: "will not route to a process if a
request previously routed to it is still in progress." This could mean that a
PHP parent with several children would not be faster than a single PHP process.
(I have not really measured this, also don't know whether mod_fastcgi and
mod_fcgid act differently in this respect.) Then your replacement would make
sense.
However, in my scenario with APC extension, the child management by a PHP
parent is even then advantageous, since crashed children are replaced without
losing the content of the APC shared-memory cache (which is created during
parent startup and is shared with the children).

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message