svn commit: r841620 - in /websites/staging/trafficserver/trunk: cgi-bin/ content/ content/docs/trunk/admin/cluster-howto/index.en.html

[bu...@apache.org]

Author: buildbot
Date: Tue Dec 11 02:10:10 2012
New Revision: 841620

Log:
Staging update by buildbot for tserver

Modified:
    websites/staging/trafficserver/trunk/cgi-bin/   (props changed)
    websites/staging/trafficserver/trunk/content/   (props changed)
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/cluster-howto/index.en.html

Propchange: websites/staging/trafficserver/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Dec 11 02:10:10 2012
@@ -1 +1 @@
-1419255
+1419975

Propchange: websites/staging/trafficserver/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Dec 11 02:10:10 2012
@@ -1 +1 @@
-1419255
+1419975

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/cluster-howto/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/cluster-howto/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/cluster-howto/index.en.html Tue Dec 11 02:10:10 2012
@@ -177,17 +177,20 @@ node, will take effect on <strong>all</s
 and we can tweak for the Cluster threads and connections:</p>
 <ul>
 <li>
-<p>Increasing Cluster threads:
- In the cluster env, the current performance of the Cluster threads will consume the same cpu
- usage as net threads, so you may adapt the ET_NET &amp; ET_CLUSTER at about 1:1. For example, on
- a 24 cores system, set ET_NET threads to 10, ET_CLUSTER threads to 10. 
-        traffic_line -s proxy.config.cluster.threads -v 10</p>
+<p>Increasing Cluster threads:</p>
+<p>In the cluster env, the current performance of the Cluster threads will consume the same cpu
+usage as net threads, so you may adapt the ET_NET &amp; ET_CLUSTER at about 1:1. For example, on
+a 24 cores system, set ET_NET threads to 10, ET_CLUSTER threads to 10. </p>
+<div class="codehilite"><pre><span class="n">traffic_line</span> <span class="o">-</span><span class="n">s</span> <span class="n">proxy</span><span class="o">.</span><span class="n">config</span><span class="o">.</span><span class="n">cluster</span><span class="o">.</span><span class="n">threads</span> <span class="o">-</span><span class="n">v</span> <span class="mi">10</span>
+</pre></div>
+
+
 </li>
 <li>
-<p>Setup the Cluster connections:
- In the Cluster, the internal connections is TCP and limited by ET_CLUSTER threads and network
- performance, we can increase the connections to archive better performance.
-    traffic_line -s proxy.config.cluster.num_of_cluster_connections -v 10</p>
+<p>Setup the Cluster connections:</p>
+<p>In the Cluster, the internal connections is TCP and limited by ET_CLUSTER threads and network
+performance, we can increase the connections to archive better performance.</p>
+<p>traffic_line -s proxy.config.cluster.num_of_cluster_connections -v 10</p>
 </li>
 </ul>
 <p>with these tweak, we can archive about 10gbps traffic for the internal cluster transfer speed.</p>