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 worker MPM to automatically bump the value of MaxSpareThreads
to at least 15% of MaxClients, with a warning written to the error log
+1 to b), btw.
we've had offline discussions about optimizing MaxSpareThreads according
to the variance seen in busy threads, but that's for admins who know
what they're doing. 15% is pretty conservative and should help sites
with less experienced admins.
Greg
+1
Bill
