You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by nd...@apache.org on 2003/01/05 05:01:19 UTC
cvs commit: httpd-2.0/docs/manual/misc perf-tuning.html.en perf-tuning.xml
nd 2003/01/04 20:01:19
Modified: docs/manual/misc Tag: APACHE_2_0_BRANCH perf-tuning.html.en
perf-tuning.xml
Log:
backport some of Brian's performance hints
Revision Changes Path
No revision
No revision
1.3.2.3 +38 -0 httpd-2.0/docs/manual/misc/perf-tuning.html.en
Index: perf-tuning.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/misc/perf-tuning.html.en,v
retrieving revision 1.3.2.2
retrieving revision 1.3.2.3
diff -u -r1.3.2.2 -r1.3.2.3
--- perf-tuning.html.en 22 Dec 2002 20:18:20 -0000 1.3.2.2
+++ perf-tuning.html.en 5 Jan 2003 04:01:19 -0000 1.3.2.3
@@ -386,6 +386,44 @@
+ <h3>Choosing an MPM</h3>
+
+
+
+ <p>Apache 2.x supports pluggable concurrency models, called
+ <a href="../mpm.html">Multi-Processing Modules</a> (MPMs).
+ When building Apache, you must choose an MPM to use. There
+ are platform-specific MPMs for some platforms:
+ <code class="module"><a href="../mod/beos.html">beos</a></code>, <code class="module"><a href="../mod/mpm_netware.html">mpm_netware</a></code>,
+ <code class="module"><a href="../mod/mpmt_os2.html">mpmt_os2</a></code>, and <code class="module"><a href="../mod/mpm_winnt.html">mpm_winnt</a></code>. For
+ general Unix-type systems, there are several MPMs from which
+ to choose. The choice of MPM can affect the speed and scalability
+ of the httpd:</p>
+
+ <ul>
+
+ <li>The <code class="module"><a href="../mod/worker.html">worker</a></code> MPM uses multiple child
+ processes with many threads each. Each thread handles
+ one connection at a time. Worker generally is a good
+ choice for high-traffic servers because it has a smaller
+ memory footprint than the prefork MPM.</li>
+
+ <li>The <code class="module"><a href="../mod/prefork.html">prefork</a></code> MPM uses multiple child
+ processes with one thread each. Each process handles
+ one connection at a time. On many systems, prefork is
+ comparable in speed to worker, but it uses more memory.
+ Prefork's threadless design has advantages over worker
+ in some situations: it can be used with non-thread-safe
+ third-party modules, and it is easier to debug on platforms
+ with poor thread debugging support.</li>
+
+ </ul>
+
+ <p>For more information on these and other MPMs, please
+ see the MPM <a href="../mpm.html">documentation</a>.</p>
+
+
+
<h3>mod_status and ExtendedStatus On</h3>
1.3.2.2 +38 -0 httpd-2.0/docs/manual/misc/perf-tuning.xml
Index: perf-tuning.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/misc/perf-tuning.xml,v
retrieving revision 1.3.2.1
retrieving revision 1.3.2.2
diff -u -r1.3.2.1 -r1.3.2.2
--- perf-tuning.xml 22 Dec 2002 20:18:20 -0000 1.3.2.1
+++ perf-tuning.xml 5 Jan 2003 04:01:19 -0000 1.3.2.2
@@ -404,6 +404,44 @@
<section>
+ <title>Choosing an MPM</title>
+
+ <p>Apache 2.x supports pluggable concurrency models, called
+ <a href="../mpm.html">Multi-Processing Modules</a> (MPMs).
+ When building Apache, you must choose an MPM to use. There
+ are platform-specific MPMs for some platforms:
+ <module>beos</module>, <module>mpm_netware</module>,
+ <module>mpmt_os2</module>, and <module>mpm_winnt</module>. For
+ general Unix-type systems, there are several MPMs from which
+ to choose. The choice of MPM can affect the speed and scalability
+ of the httpd:</p>
+
+ <ul>
+
+ <li>The <module>worker</module> MPM uses multiple child
+ processes with many threads each. Each thread handles
+ one connection at a time. Worker generally is a good
+ choice for high-traffic servers because it has a smaller
+ memory footprint than the prefork MPM.</li>
+
+ <li>The <module>prefork</module> MPM uses multiple child
+ processes with one thread each. Each process handles
+ one connection at a time. On many systems, prefork is
+ comparable in speed to worker, but it uses more memory.
+ Prefork's threadless design has advantages over worker
+ in some situations: it can be used with non-thread-safe
+ third-party modules, and it is easier to debug on platforms
+ with poor thread debugging support.</li>
+
+ </ul>
+
+ <p>For more information on these and other MPMs, please
+ see the MPM <a href="../mpm.html">documentation</a>.</p>
+
+ </section>
+
+ <section>
+
<title>mod_status and ExtendedStatus On</title>
<p>If you include <module>mod_status</module> and you also set