From: Ryan Bloom Date: Sun, 19 Nov 2000 21:52:50 +0000 (+0000) Subject: Add some docs to the common MPM directives. X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=dde1f575f002f664c6d5561dab9d6334e26721e3;p=apache Add some docs to the common MPM directives. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@87031 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mpm_common.html b/docs/manual/mod/mpm_common.html index 2381122704..d29dbc9fd8 100644 --- a/docs/manual/mod/mpm_common.html +++ b/docs/manual/mod/mpm_common.html @@ -47,11 +47,13 @@ than one multi-processing module (MPM).

Syntax:
+>Syntax: + ConnectionStatus {on,off}
Default:
+>Default: + ConnectionStatus on
Module: dexter, perchild

Whether or not to maintain status information on current -connections

+connections. If this is off then mod_status will not work properly.

@@ -423,7 +425,7 @@ behavior to limit the number of connections per child. Default: MaxSpareThreads ??
+>Default: MaxSpareThreads 10 (Dexter or Perchild) or 500 (Mpmt_pthread)
connections per child. REL="Help" >Module: dexter, mpmt_pthread, perchild

-

Maximum number of idle threads.

+

Maximum number of idle threads. Different MPMs deal with this directive +differently. Dexter and Perchild monitor the number of idle threads on a +per-child basis. If there are too many idle threads in that child, the server +will begin to kill threads within that child.

+

Mpmt_pthread deals with idle threads on a server-wide basis. If there are +too many idle threads in the server then child processes are killed +until the number of idle threads is less than this number.

See also MinSpareThreads and StartServers. @@ -453,7 +461,7 @@ behavior to limit the number of connections per child. Default: MinSpareServers ???
+>Default: MaxSpareThreads 5 (Dexter or Perchild) or 250 (Mpmt_pthread)
connections per child. REL="Help" >Module: dexter, mpmt_pthread, perchild

-

Minimum number of idle threads to handle request spikes. +

Minimum number of idle threads to handle request spikes. Different MPMs +deal with this directive differently. Dexter and Perchild monitor the number +of idle threads on a per-child basis. If there aren't enough idle threads in +that child, the server will begin to create new threads within that child. +

+

Mpmt_pthread deals with idle threads on a server-wide basis. If there +aren't enough idle threads in the server then child processes are created +until the number of idle threads is greater than number.

See also MaxSpareThreads and StartServers.

@@ -477,11 +492,11 @@ See also MaxSpareThreads and

Syntax:
+>Syntax: NumServers number
Default:
+>Default: NumServers 2
MaxSpareThreads and REL="Help" >Module: dexter, perchild

-

Number of children alive at the same time.

+

Number of children alive at the same time. MPMs that use this directive +do not dynamically create new child processes so this number should be +large enough to handle the requests for the entire site.

@@ -607,11 +624,11 @@ on the load, there is usually little reason to adjust this parameter.

Syntax:
+>Syntax: StartThreads number
Default:
+>Default: StartThreads 5
REL="Help" >Module: dexter, perchild

-

Number of threads each child creates.

+

Number of threads each child creates on startup. As the number of threads +is dynamically controlled depending on the load, there is usually little +reason to adjust this parameter.

@@ -652,7 +671,12 @@ on the load, there is usually little reason to adjust this parameter.

>Module: mpmt_pthread, mpm_winnt

This directive sets the number of threads created by each child -process.

+process. The child creates these threads at startup and never creates +more. if using an MPM like mpmt_winnt, where there is only one child process, +this number should be high enough to handle the entire load of the server. +If using an MPM like mpmt_pthread, where there are multiple child processes, +the total number of threads should be high enough to handle the common load +on the server.