some docco updates

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

diff --git a/docs/manual/mod/mod_lbmethod_bybusyness.xml b/docs/manual/mod/mod_lbmethod_bybusyness.xml
index 8b9cb3b45716dfd3d216f66512953e6bb759c173..48c537e94d32132150f89d0d9234166426948f0d 100644 (file)
--- a/docs/manual/mod/mod_lbmethod_bybusyness.xml
+++ b/docs/manual/mod/mod_lbmethod_bybusyness.xml
@@ -43,17 +43,18 @@ provides the <code>bybusyness</code> load balancing method.</p>
     <title>Pending Request Counting Algorithm</title>
 
     <p>Enabled via <code>lbmethod=bybusyness</code>, this scheduler keeps
-    track of how many requests each worker is assigned at present. A new
+    track of how many requests each worker is currently assigned at present. A new
     request is automatically assigned to the worker with the lowest
     number of active requests. This is useful in the case of workers
     that queue incoming requests independently of Apache, to ensure that
     queue length stays even and a request is always given to the worker
-    most likely to service it fastest.</p>
+    most likely to service it the fastest and reduce latency.</p>
 
     <p>In the case of multiple least-busy workers, the statistics (and
     weightings) used by the Request Counting method are used to break the
     tie. Over time, the distribution of work will come to resemble that
-    characteristic of <code>byrequests</code>.</p>
+    characteristic of <code>byrequests</code> (as implemented
+    by <module>mod_lbmethod_byrequests</module>).</p>
 
 </section>
 

diff --git a/docs/manual/mod/mod_lbmethod_bytraffic.xml b/docs/manual/mod/mod_lbmethod_bytraffic.xml
index d4a0302484a1f723016dfebe994d54f119329f66..989328b9c2333bad5c74afdf5c8f65c761aa2233 100644 (file)
--- a/docs/manual/mod/mod_lbmethod_bytraffic.xml
+++ b/docs/manual/mod/mod_lbmethod_bytraffic.xml
@@ -48,7 +48,8 @@ provides the <code>bytraffic</code> load balancing method..</p>
     this worker to handle</em>. This is also a normalized value
     representing their "share" of the amount of work to be done,
     but instead of simply counting the number of requests, we take
-    into account the amount of traffic this worker has seen.</p>
+    into account the amount of traffic this worker has either seen
+    or produced.</p>
 
     <p>If a balancer is configured as follows:</p>
     
@@ -70,6 +71,8 @@ provides the <code>bytraffic</code> load balancing method..</p>
     size of the request and response are applied to the weighting
     and selection algorithm.</p>
 
+    <p>Note: input and output bytes are weighted the same.</p>
+
 </section>
 
 </modulesynopsis>