Server max-workerDetails » History » Revision 7
Revision 6 (stbuehler, 2008-10-11 11:24) → Revision 7/16 (nitrox, 2010-08-17 12:29)
h2. server.max-worker option
*{color:red}DO NOT USE THIS OPTION IF YOU DON'T UNDERSTAND WHAT IT DOES*
*{color:red}DO NOT REPORT ERRORS OR BUGS IF YOU DID NOT TEST WITHOUT THIS OPTION SET*
*{color:red}THIS OPTION MOST LIKELY WILL NOT BOOST YOUR PERFORMANCE, ITS MOST LIKELY YOUR BACKEND THATS SLOW* BACKEND*
server.max-worker
p((. number of worker processes to spawn. This is usually only needed on servers which are fairly loaded and the network handler calls delay often (e.g. new requests are not handled instantaneously).
p((. Default: 0
p((. If you use server.max-worker, the mod_status module will not show the statistics of all the server's children combined. You will see different stats with each request. [[lighttpd:Docs:ModStatus|mod_status documentation]]
p((. Other modules are affected by this, too; every worker works for his own and there is no communication between them. Your log files may get screwed.
h2. See Also
* [[lighttpd:Docs:MultiProcessor|server.max-worker and Multiprocessors (SMP)]]