You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by el...@apache.org on 2016/12/04 10:07:56 UTC
svn commit: r1772512 - /httpd/httpd/trunk/docs/manual/mod/event.xml
Author: elukey
Date: Sun Dec 4 10:07:56 2016
New Revision: 1772512
URL: http://svn.apache.org/viewvc?rev=1772512&view=rev
Log:
Added some notes in mpm-event's doc page
Modified:
httpd/httpd/trunk/docs/manual/mod/event.xml
Modified: httpd/httpd/trunk/docs/manual/mod/event.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/event.xml?rev=1772512&r1=1772511&r2=1772512&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/event.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/event.xml Sun Dec 4 10:07:56 2016
@@ -144,7 +144,17 @@ of the <directive>AsyncRequestWorkerFact
graceful terminations in a much better way. Some of the improvements are:</p>
<ul>
<li>Allow the use of all the scoreboard slots up to
- <directive module="mpm_common">ServerLimit</directive>.</li>
+ <directive module="mpm_common">ServerLimit</directive>.
+ <directive module="mpm_common">MaxRequestWorkers</directive> and
+ <directive module="mpm_common">ThreadsPerChild</directive> are used
+ to limit the amount of active processes, meanwhile
+ <directive module="mpm_common">ServerLimit</directive>
+ takes also into account the ones doing a graceful
+ close to allow extra slots when needed. The idea is to use
+ <directive module="mpm_common">ServerLimit</directive> to instruct httpd
+ about how many overall processes are tolerated before impacting
+ the system resources.
+ </li>
<li>Force gracefully finishing processes to close their
connections in keep-alive state.</li>
<li>During graceful shutdown, if there are more running worker threads