Ok, now it makes sense :) I suggest your explanation gets
added to the docs and linked as a "See also" for all the directives involved.
Cheers
Daniel
---
Sure, but...
Here is how I would have them configured with prefork:
MaxClients: big enough to handle normal, expected load
ServerLimit: as large as is reasonable for the machine without
wasting a lot of shared memory
If my server load goes up and clients start to get
big delays or even
get connection-refused from the kernel because the queues are growing
too long, then I'd want to bump up MaxClients and do a graceful
restart and keep everybody happy.
If you limit yourself to only one directive to control this then you
either have painful, connection-dropping restarts to deal with
unexpectedly high activity or you allow Apache to grow into
unexpectedly high resource usage without you being in on the
decision, because our simple method of dealing with graceful restart
requires that the allocated size of the scoreboard stay the same.
Most folks aren't going to deal with ServerLimit or ThreadLimit
because the default values are reasonable (or we ought to fix them!),
or at least reasonable for the smaller machines.
