Server max-workerDetails » History » Revision 9
Revision 8 (nitrox, 2012-08-11 10:42) → Revision 9/16 (gstrauss, 2021-07-17 01:36)
h2. server.max-worker option @server.max-worker = 0@ - *{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* server.max-worker p((. number of worker processes to spawn (default: 0) @server.max-worker = 0@ spawn. This is strongly recommended, using the least resources usually only needed on servers which are fairly loaded and being the most performant, except in [[Docs_MultiProcessor|specific uses cases for multiple lighttpd workers]]. network handler calls delay often (e.g. new requests are not handled instantaneously). Note that [[lighttpd:Docs_ModStatus|mod_status]] does p((. Default: 0 p((. If you use server.max-worker, the mod_status module will not provide aggregate show the statistics when @server.max-worker@ > 1. There 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 also limitations with some other, less frequently used modules, discussed in [[Docs_MultiProcessor|specific uses cases affected by this, too; every worker works for multiple lighttpd workers]] 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)]]