Selecting an MPM in performance docs.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1367031 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/misc/perf-scaling.xml b/docs/manual/misc/perf-scaling.xml
index 832dc8e877023b82b02c870a8551df44d8a04cbf..d84ebc6ee3a9ee004349436b67a89eb3b4d872b0 100644 (file)
--- a/docs/manual/misc/perf-scaling.xml
+++ b/docs/manual/misc/perf-scaling.xml
@@ -869,7 +869,7 @@
         
         
         <section id="apache-configuration">
-            <title>Apache Configuration
+            <title>Httpd Configuration
             </title>
             <p>The Apache 2.2 httpd is by default a pre-forking web server.
                 When the server starts, the parent process spawns a number of
@@ -897,6 +897,12 @@
                 denied access. However, once requests start backing up, system
                 performance is likely to degrade. 
             </p>
+                       <p>Finally, if the httpd server in question is not executing any third-party
+               code, via <code>mod_php</code>, <code>mod_perl</code> or similar,
+               we recommend the use of <module>mpm_event</module>. This MPM is ideal
+               for situations where httpd serves as a thin layer between clients and
+               backend servers doing the real job, such as a proxy or cache.
+            </p>
             
             
             <section id="MaxClients">