httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@apache.org
Subject cvs commit: httpd-2.0/docs/manual/misc perf-tuning.xml perf-tuning.html.en
Date Mon, 04 Aug 2003 16:51:47 GMT
slive       2003/08/04 09:51:47

  Modified:    docs/manual/misc Tag: APACHE_2_0_BRANCH perf-tuning.xml
                        perf-tuning.html.en
  Log:
  Backport removal of warning on perf-tuning.
  
  Revision  Changes    Path
  No                   revision
  No                   revision
  1.3.2.10  +11 -9     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.9
  retrieving revision 1.3.2.10
  diff -u -d -b -u -r1.3.2.9 -r1.3.2.10
  --- perf-tuning.xml	10 May 2003 00:45:05 -0000	1.3.2.9
  +++ perf-tuning.xml	4 Aug 2003 16:51:47 -0000	1.3.2.10
  @@ -9,15 +9,6 @@
   
     <summary>
   
  -    <note type="warning"><title>Warning:</title>
  -      <p>This document has not been fully updated
  -      to take into account changes made in the 2.0 version of the
  -      Apache HTTP Server. Some of the information may still be
  -      relevant, but please use it with care.</p>
  -    </note>
  -
  -    <p>Orignally written by Dean Gaudet.</p>
  -
       <p>Apache 2.0 is a general-purpose webserver, designed to
       provide a balance of flexibility, portability, and performance.
       Although it has not been designed specifically to set benchmark
  @@ -557,6 +548,13 @@
   
         <title>accept Serialization - multiple sockets</title>
   
  +    <note type="warning"><title>Warning:</title>
  +      <p>This section has not been fully updated
  +      to take into account changes made in the 2.0 version of the
  +      Apache HTTP Server. Some of the information may still be
  +      relevant, but please use it with care.</p>
  +    </note>
  +
         <p>This discusses a shortcoming in the Unix socket API. Suppose
         your web server uses multiple <directive module="mpm_common"
         >Listen</directive> statements to listen on either multiple
  @@ -688,6 +686,10 @@
         architectures it is unsafe to use multiple
         <directive module="mpm_common">Listen</directive>
         directives.</p>
  +
  +      <p>The directive <directive
  +      module="mpm_common">AcceptMutex</directive> can be used to
  +      change the selected mutuex implimentation at run-time.</p>
   
         <dl>
           <dt><code>USE_FLOCK_SERIALIZED_ACCEPT</code></dt>
  
  
  
  1.3.2.9   +10 -9     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.8
  retrieving revision 1.3.2.9
  diff -u -d -b -u -r1.3.2.8 -r1.3.2.9
  --- perf-tuning.html.en	29 May 2003 19:29:43 -0000	1.3.2.8
  +++ perf-tuning.html.en	4 Aug 2003 16:51:47 -0000	1.3.2.9
  @@ -22,15 +22,6 @@
   </div>
   
   
  -    <div class="warning"><h3>Warning:</h3>
  -      <p>This document has not been fully updated
  -      to take into account changes made in the 2.0 version of the
  -      Apache HTTP Server. Some of the information may still be
  -      relevant, but please use it with care.</p>
  -    </div>
  -
  -    <p>Orignally written by Dean Gaudet.</p>
  -
       <p>Apache 2.0 is a general-purpose webserver, designed to
       provide a balance of flexibility, portability, and performance.
       Although it has not been designed specifically to set benchmark
  @@ -544,6 +535,13 @@
   
         
   
  +    <div class="warning"><h3>Warning:</h3>
  +      <p>This section has not been fully updated
  +      to take into account changes made in the 2.0 version of the
  +      Apache HTTP Server. Some of the information may still be
  +      relevant, but please use it with care.</p>
  +    </div>
  +
         <p>This discusses a shortcoming in the Unix socket API. Suppose
         your web server uses multiple <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>
statements to listen on either multiple
         ports or multiple addresses. In order to test each socket
  @@ -673,6 +671,9 @@
         architectures it is unsafe to use multiple
         <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code>
         directives.</p>
  +
  +      <p>The directive <code class="directive"><a href="../mod/mpm_common.html#acceptmutex">AcceptMutex</a></code>
can be used to
  +      change the selected mutuex implimentation at run-time.</p>
   
         <dl>
           <dt><code>USE_FLOCK_SERIALIZED_ACCEPT</code></dt>
  
  
  

Mime
View raw message