You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by je...@apache.org on 2001/08/12 20:00:03 UTC
cvs commit: httpd-2.0/docs/conf httpd-std.conf
jerenkrantz 01/08/12 11:00:03
Modified: docs/conf httpd-std.conf
Log:
Change the MaxSpareThreads to 150 for threaded MPM. This mirrors the new
prefork setting and removes the default case where we would spawn three
children, but kill two of them immediately because MaxSpareThreads was
set to 10 (only one children can be supported with the old value).
Please note that I don't have email access as eBuilt's servers are AWOL
this weekend (none of us have the desire to go in a fix the servers for
semi-obvious reasons). I'm trying to keep up on posts via apachelabs.org.
So, if you want to change this, just go ahead and commit the changes...
Revision Changes Path
1.35 +1 -1 httpd-2.0/docs/conf/httpd-std.conf
Index: httpd-std.conf
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/conf/httpd-std.conf,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- httpd-std.conf 2001/08/12 15:44:18 1.34
+++ httpd-std.conf 2001/08/12 18:00:03 1.35
@@ -131,7 +131,7 @@
StartServers 3
MaxClients 8
MinSpareThreads 5
-MaxSpareThreads 10
+MaxSpareThreads 150
ThreadsPerChild 25
MaxRequestsPerChild 0
</IfModule>
Re: cvs commit: httpd-2.0/docs/conf httpd-std.conf
Posted by Sander Temme <sc...@covalent.net>.
on 8/12/01 11:23 AM, Joshua Slive at joshua@slive.ca wrote:
> MaxSpareThreads should not mirror MaxClients in prefork. They do
> completely different things. I agree with your analysis that shows that
> MaxSpareThreads should be higher. But 150 seems excessive.
> I think the problem is that ThreadsPerChild is too high for
> a lightly loaded site. My suggestion is:
>
> StartServers 3
> MaxClients 15
> MinSpareThreads 5
> MaxSpareThreads 30
> ThreadsPerChild 10
> MaxRequestsPerChild 0
>
Note that HARD_SERVER_LIMIT is currently (that is, in the 2.0.23 tarball) at
8 for threaded.
S.
--
Covalent Technologies sctemme@covalent.net
Engineering group Voice: (415) 536 5214
645 Howard St. Fax: (415) 536 5210
San Francisco CA 94105
PGP Fingerprint: 1E74 4E58 DFAC 2CF5 6A03 5531 AFB1 96AF B584 0AB1
=======================================================
This email message is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and destroy all copies
of the original message
=======================================================
Re: cvs commit: httpd-2.0/docs/conf httpd-std.conf
Posted by Joshua Slive <jo...@slive.ca>.
On 12 Aug 2001 jerenkrantz@apache.org wrote:
> jerenkrantz 01/08/12 11:00:03
>
> Modified: docs/conf httpd-std.conf
> Log:
> Change the MaxSpareThreads to 150 for threaded MPM. This mirrors the new
> prefork setting and removes the default case where we would spawn three
> children, but kill two of them immediately because MaxSpareThreads was
> set to 10 (only one children can be supported with the old value).
MaxSpareThreads should not mirror MaxClients in prefork. They do
completely different things. I agree with your analysis that shows that
MaxSpareThreads should be higher. But 150 seems excessive.
I think the problem is that ThreadsPerChild is too high for
a lightly loaded site. My suggestion is:
StartServers 3
MaxClients 15
MinSpareThreads 5
MaxSpareThreads 30
ThreadsPerChild 10
MaxRequestsPerChild 0
This makes MaxClients*ThreadsPerChild=150 which matches the
effect of MaxClients=150 in prefork. It also makes
StartServers*ThreadsPerChild=30=MaxSpareThreads which
should get rid of the thrashing.
People running busier sites can raise ThreadsPerChild once
they are confident they have a working configuration.
Any objections?
I guess this also points out that someone needs to get back into that
argument about claryifying all the MPM directives.
Joshua.