httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <>
Subject Re: MPM default config and conf/extra/httpd-mpm.conf
Date Tue, 15 Jun 2010 21:15:30 GMT
On 15.06.2010 22:51, Igor Galić wrote:
> ----- "Rainer Jung"<>  wrote:
>> I noticed, that the values in conf/extra/httpd-mpm.conf in parts
>> differ
>> hugely from the corresponding MPM defaults.
>> IMHO activating conf/extra/httpd-mpm.conf should be safe in the sense
>> that you don't get changed MPM behaviour as long as you don't change
>> the
>> file contents. If we think the values in conf/extra/httpd-mpm.conf are
>> better than the defaults, those should be the defaults.
>> If people agree, I would first correct conf/extra/httpd-mpm.conf to
>> contain the actual defaults, and of course if we think those are not
>> good, we can then improve them.
>> Examples:
>> - MaxRequestsPerChild (for most MPMs default is 10000 - pretty low
>> nowadays, in the config it's "0")
>> - MaxClients for event and worker: default 400, in the config 250
>> ... many more ...
> I wonder if this thread is wrong enough for the topic:
> Would it be possible to choose defaults for the MPMs based on
> the available CPU(core)s and the Memory, rather than just hard
> coding the values?

I doubt it's worth it and that we can make it work nicely. I think we 
are looking for a mid-size configuration that neither optimizes on tiny 
systems (saving as much resources as possible) nor on high load systems 
(extreme scaling) but instead for the huge number on configurations in 
between, that hope to work reasonable with default sizing.

If we are talking about auto-detecting system resources: Memory and CPU 
in these cases often is not only used for httpd because it is not the 
only application on the system.

If we want the user to assign those resources I doubt we can find good 


View raw message