294N/A<!
DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
787N/A<
TITLE>Server Pool Management</
TITLE>
294N/A<
BODY BGCOLOR="white" TEXT="black" LINK="blue" VLINK="navy" ALINK="red">
787N/A<
H1 ALIGN="CENTER">Server Pool Management</
H1>
294N/AWe found that many people were using values for "MaxServers" either
294N/Atoo high or too low, and were hanging themselves on it. The model we
294N/Aadopted is still based on long-lived minimal-forking processes, but
294N/Ainstead of specifying one number of persistent processes, the
294N/Aweb-master specifies a maximum and minimum number of processes to be
294N/A"spare" - every couple of seconds the parent checks the actual number
787N/Aof spare servers and adjusts accordingly. This should keep the number
787N/Aof servers concurrently running relatively low while still ensuring
294N/AWe renamed the current StartServers to MinSpareServers, created
294N/Aseparate StartServers parameter which means what it says, and renamed
294N/AMaxServers to MaxSpareServers (though the old name still works, for
294N/ANCSA 1.4 back-compatibility). The old names were generally regarded
294N/AThe defaults for each variable are:
294N/AThere is an absolute maximum number of simultaneous children defined
294N/Aby a compile-time limit which defaults to 256 and a "MaxClients"
294N/Adirective which specifies the number of simultaneous children that
294N/Awill be allowed. MaxClients can be adjusted up to the compile-time
294N/Alimit (HARD_SERVER_LIMIT, defined in
httpd.h). If you need more
787N/Athan 256 simultaneous children, you need to modify both HARD_SERVER_LIMIT
294N/AIn versions before 1.2, HARD_SERVER_LIMIT defaulted to 150.<
P>
294N/AWe do not recommend changing either of these values unless:
787N/A<
LI>You know you have the server resources to handle more
294N/A<
LI>You use the machine for other purposes and must limit the amount of memory