You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2011/11/13 16:45:22 UTC
DO NOT REPLY [Bug 52174] New: Allow hard lower-limits on the number
of fcgi service processes
https://issues.apache.org/bugzilla/show_bug.cgi?id=52174
Bug #: 52174
Summary: Allow hard lower-limits on the number of fcgi service
processes
Product: Apache httpd-2
Version: 2.4-HEAD
Platform: All
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: mod_fcgid
AssignedTo: bugs@httpd.apache.org
ReportedBy: danny-bugzilla@sadinoff.com
Classification: Unclassified
I have FCGI processes that take a long time (~30 seconds) to start and
initialize.
mod_fcgid's approach is to fork new ones on demand, but that often takes too
long in my scenario.
My goal is to ensure that there are at least N of them spun up and ready at any
time.
The docs say that FcgidMinProcessesPerClass enforces a...
"minimum number of processes that will be retained in a process class after
finishing requests"
My suggestion is to create a new config variable, say
"FcgidHardMinProcessesPerClass" which would be the minimum number of processes
that ought to exist for a class at all times, even before the first request
arrives. If the number of servers dips below that amount, it would fork a new
one.
--
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
DO NOT REPLY [Bug 52174] Allow hard lower-limits on the number of
fcgi service processes
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=52174
--- Comment #1 from Danny Sadinoff <da...@sadinoff.com> 2011-11-16 12:59:28 UTC ---
If mod_fcgid is tasked with maintaining client processes before the first
request, that puts it in the uncomfortable position of having to make up
requests.
An alternate approach might be to promise that the first X requests will spawn
unconditionally, making it more predictable how to front-load the initial
spawning requests.
--
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