|
Apache HTTP Server Version 2.2   Apache MPM prefork
SummaryThis Multi-Processing Module (MPM) implements a non-threaded, pre-forking web server that handles requests in a manner similar to Apache 1.3. It is appropriate for sites that need to avoid threading for compatibility with non-thread-safe libraries. It is also the best MPM for isolating each request, so that a problem with a single request will not affect any other. This MPM is very self-regulating, so it is rarely necessary to
adjust its configuration directives. Most important is that
Directives
TopicsSee also How it WorksA single control process is responsible for launching child processes which listen for connections and serve them when they arrive. Apache always tries to maintain several spare or idle server processes, which stand ready to serve incoming requests. In this way, clients do not need to wait for a new child processes to be forked before their requests can be served. TheStartServers,
MinSpareServers,
MaxSpareServers, and
MaxClients regulate how
the parent process creates children to serve requests. In general,
Apache is very self-regulating, so most sites do not need to
adjust these directives from their default values. Sites which
need to serve more than 256 simultaneous requests may need to
increase MaxClients,
while sites with limited memory may need to decrease MaxClients to keep the server from
thrashing (swapping memory to disk and back). More information
about tuning process creation is provided in the performance hints
documentation.
While the parent process is usually started as
MaxSpareServers Directive
The Tuning of this parameter should only be necessary on very
busy sites. Setting this parameter to a large number is almost
always a bad idea. If you are trying to set the value equal to or lower than
See alsoMinSpareServers Directive
The Tuning of this parameter should only be necessary on very busy sites. Setting this parameter to a large number is almost always a bad idea. See also |
