Aaron Bannert wrote:
Just so I understand the problem correctly,
but that since the turnover is so quick you end up having children
lingering around with one or two thread slots and essentially
we approach the prefork scenario in terms of number of child
processes. Is this correct?
in worker +
Jeff Trawick wrote:
Then realize you need to support boatloads more clients, so you bump
up MaxClients to 5000. Now when load changes very slightly (as a
percentage of MaxClients), which happens continuously, the web server
will create or destroy a child process.
b) tweak worker MPM to
Greg Ames wrote:
Jeff Trawick wrote:
Then realize you need to support boatloads more clients, so you bump
up MaxClients to 5000. Now when load changes very slightly (as a
percentage of MaxClients), which happens continuously, the web server
will create or destroy a child process.
b) tweak
On Mar 4, 2005, at 12:08 PM, Jeff Trawick wrote:
Any comments on these two separate proposals?
b) tweak worker MPM to automatically bump the value of MaxSpareThreads
to at least 15% of MaxClients, with a warning written to the error log
I like this best, because is requires no action on the user's
On Mon, 7 Mar 2005 08:35:12 -0800, Aaron Bannert [EMAIL PROTECTED] wrote:
On Mar 4, 2005, at 12:08 PM, Jeff Trawick wrote:
Any comments on these two separate proposals?
b) tweak worker MPM to automatically bump the value of MaxSpareThreads
to at least 15% of MaxClients, with a warning
Start with something like this:
MaxClients 150
...
MaxSpareThreads 75
in the default conf file, which is a very reasonable way to run.
Then realize you need to support boatloads more clients, so you bump
up MaxClients to 5000. Now when load changes very slightly (as a
percentage of
