Apache 1.3.33 - what would this server parameter set do?

[thedaver]

Opinions please on the practical benefits and limits of the following httpd.conf segment. I'm trying to debug an application problem. I'm trying to unravel why the developer selected this particular configuration.

MinSpareServers 20
MaxSpareServers 20
StartServers 20
MaxClients 20
MaxRequestsPerChild 1024

Thanks in advance!
D

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/

 

[elgrandeperro]

Because they didn't know what they were doing. Is this a windows server?

Apache manages subprocesses to avoid the overload of creating new processes or processing dead ones.

So this says start 20, keep at least 20 "idle" ones both at a min and max, and have a max of 20 doing requests!

The maxrequests says after 1024 requests completed by a child, respawn (I usually use this for memory/garbage problems.

StartServers is always smaller there is no reason to spin up 20 processes.

MinSpare should be < MaxSpare and should not be close to MaxClients.

This is the apache recommendations:

MinSpareServers 5
MaxSpareServers 10
StartServers 5
MaxClients 255
MaxRequestsPerChild 0 (with caveats)

 

[thedaver]

Yeah, it's weird from a linux kit on a proprietary app.

I read this as:

Start 20, keep 20 spare (min/max) and only allow 20.
I'd hate to be the 21st connection... ;-)

Since the backend app is a perl app, the marequests doesn't seem that insane, but it does imply a rather lot of respawning if things get busy.

Thx!

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/