[hornetq-commits] JBoss hornetq SVN: r9205 - trunk/docs/user-manual/en.

[do-not-reply at jboss.org]

Author: timfox
Date: 2010-05-06 12:18:59 -0400 (Thu, 06 May 2010)
New Revision: 9205

Modified:
   trunk/docs/user-manual/en/perf-tuning.xml
   trunk/docs/user-manual/en/wildcard-routing.xml
Log:
a couple of tweaks to docs

Modified: trunk/docs/user-manual/en/perf-tuning.xml
===================================================================
--- trunk/docs/user-manual/en/perf-tuning.xml	2010-05-06 15:45:35 UTC (rev 9204)
+++ trunk/docs/user-manual/en/perf-tuning.xml	2010-05-06 16:18:59 UTC (rev 9205)
@@ -154,6 +154,9 @@
                     for more information.</para>
             </listitem>
             <listitem>
+                <para>If you have very fast consumers, you can increase consumer-window-size. This effectively disables consumer flow control.</para>
+            </listitem>
+            <listitem>
                 <para>Socket NIO vs Socket Old IO. By default HornetQ uses Socket NIO on the server
                     and old (blocking) IO on the client side (see the chapter on configuring
                     transports for more information <xref linkend="configuring-transports"/>). NIO
@@ -177,18 +180,8 @@
     </section>
     <section>
         <title>Tuning Transport Settings</title>
-        <itemizedlist>
+        <itemizedlist>            
             <listitem>
-                <para>Enable <ulink url="http://en.wikipedia.org/wiki/Nagle's_algorithm">Nagle's
-                        algorithm</ulink>. If you are sending many small messages, such that more
-                    than one can fit in a single IP packet thus providing better performance. This
-                    is done by setting <literal>tcp-no-delay</literal> to false with the Netty
-                    transports. See <xref linkend="configuring-transports"/> for more information on
-                    this. </para>
-                <para>Enabling Nagle's algorithm can make a very big difference in performance and
-                    is highly recommended if you're sending a lot of asynchronous traffice.</para>
-            </listitem>
-            <listitem>
                 <para>TCP buffer sizes. If you have a fast network and fast machines you may get a
                     performance boost by increasing the TCP send and receive buffer sizes. See the
                         <xref linkend="configuring-transports"/> for more information on this.

Modified: trunk/docs/user-manual/en/wildcard-routing.xml
===================================================================
--- trunk/docs/user-manual/en/wildcard-routing.xml	2010-05-06 15:45:35 UTC (rev 9204)
+++ trunk/docs/user-manual/en/wildcard-routing.xml	2010-05-06 16:18:59 UTC (rev 9205)
@@ -21,12 +21,11 @@
 <chapter id="wildcard-routing">
     <title>Routing Messages With Wild Cards</title>
     <para>HornetQ allows the routing of messages via wildcard addresses.</para>
-    <para>If a consumer is created with an address of say <literal>queue.news.#</literal> then it
+    <para>If a queue is created with an address of say <literal>queue.news.#</literal> then it
         will receive any messages sent to addresses that match this, for instance <literal
             >queue.news.europe</literal> or <literal>queue.news.usa</literal> or <literal
-            >queue.news.usa.sport</literal>. This allows a consumer to consume messages which are
-        sent to a <emphasis>hierarchy</emphasis> of addresses, rather than the consumer having to
-        specify a specific address.</para>
+            >queue.news.usa.sport</literal>. If you create a consumer on this queue, this allows a consumer to consume messages which are
+        sent to a <emphasis>hierarchy</emphasis> of addresses.</para>
     <note>
         <para>In JMS terminology this allows "topic hierarchies" to be created.</para>
     </note>