svn commit - mysqldoc@docsrva: r9531 - in trunk: dynamic-docs/changelog dynamic-docs/command-optvars refman-5.1

[jon]

Author: jstephens
Date: 2008-01-09 17:25:45 +0100 (Wed, 09 Jan 2008)
New Revision: 9531

Log:

Documented ndb_optimization_delay global system variable - for NDB 
OPTIMIZE TABLE/CGE 6.3.7 (Thanks, Martin!)



Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/dynamic-docs/command-optvars/mysqld.xml
   trunk/refman-5.1/mysql-cluster-cge.xml
   trunk/refman-5.1/mysql-cluster-limitations.xml
   trunk/refman-5.1/sql-syntax.xml


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2008-01-09 16:10:01 UTC (rev 9530)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2008-01-09 16:25:45 UTC (rev 9531)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 0; 750 bytes

@@ -116,6 +116,13 @@
         <literal>DELETE</literal>.
       </para>
 
+      <para>
+        The performance of <literal>OPTIMIZE</literal> on
+        <literal>NDB</literal> tables can be regulated by adjusting the
+        value of the <literal>ndb_optimization_delay</literal> system
+        variable.
+      </para>
+
     </message>
 
   </logentry>

@@ -4443,6 +4450,7 @@
 
     <tags>
       <manual type="Falcon"/>
+      <highlight type="partitioning"/>
     </tags>
 
     <bugs>


Modified: trunk/dynamic-docs/command-optvars/mysqld.xml
===================================================================
--- trunk/dynamic-docs/command-optvars/mysqld.xml	2008-01-09 16:10:01 UTC (rev 9530)
+++ trunk/dynamic-docs/command-optvars/mysqld.xml	2008-01-09 16:25:45 UTC (rev 9531)
Changed blocks: 2, Lines Added: 31, Lines Deleted: 1; 1386 bytes

@@ -13155,6 +13155,32 @@
 
   </mysqloption>
 
+  <mysqloption id="ndb_optimization_delay">
+
+    <name>ndb_optimization_delay</name>
+
+    <shortdescription lang="en">
+      Sets the number of milliseconds to wait between processing sets of
+      rows by OPTIMIZE TABLE on NDB tables.
+    </shortdescription>
+
+    <types>
+      <vartype class="system" scope="global" isdynamic="yes"/>
+    </types>
+
+    <values vartype="numeric" platform="all">
+
+      <value minimum="0" maximum="100000" default="10"/>
+
+    </values>
+
+    <versions>
+      <introduced version="5.1.23-ndb-6.3.7"/>
+      <manual version="5.1"/>
+    </versions>
+
+  </mysqloption>
+
   <mysqloption section="ndb" id="ndb_autoincrement_prefetch_sz">
 
     <name>ndb-autoincrement-prefetch-sz</name>

@@ -17876,8 +17902,12 @@
       <vartype class="system" scope="session" isdynamic="yes"/>
     </types>
 
-    <values vartype="boolean" platform="all"></values>
+    <values vartype="boolean" platform="all">
 
+      <value default="FALSE"/>
+
+    </values>
+
     <versions>
       <introduced version="5.1.23-ndb-6.3.7"/>
       <manual version="5.1"/>


Modified: trunk/refman-5.1/mysql-cluster-cge.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-cge.xml	2008-01-09 16:10:01 UTC (rev 9530)
+++ trunk/refman-5.1/mysql-cluster-cge.xml	2008-01-09 16:25:45 UTC (rev 9531)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 1; 1045 bytes

@@ -778,7 +778,13 @@
               such cases, it is no longer necessary to drop (and
               possibly to re-create) a table, or to perform a rolling
               restart, in order to recover memory from deleted rows for
-              general re-use by Cluster. (MySQL 5.1.23-ndb-6.3.7)
+              general re-use by Cluster. The performance of
+              <literal>OPTIMIZE</literal> on Cluster tables can be tuned
+              by adjusting the value of the
+              <literal>ndb_optimization_delay</literal> system variable,
+              which controls the number of milliseconds to wait between
+              processing batches of rows by <literal>OPTIMIZE
+              TABLE</literal>. (MySQL 5.1.23-ndb-6.3.7)
             </para>
           </listitem>
 


Modified: trunk/refman-5.1/mysql-cluster-limitations.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-limitations.xml	2008-01-09 16:10:01 UTC (rev 9530)
+++ trunk/refman-5.1/mysql-cluster-limitations.xml	2008-01-09 16:25:45 UTC (rev 9531)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 0; 1043 bytes

@@ -1922,6 +1922,17 @@
                 </listitem>
 
               </itemizedlist>
+
+              You can regulate the effects of
+              <literal>OPTIMIZE</literal> on performance by adjusting
+              the value of the global system variable
+              <literal>ndb_optimization_delay</literal>, which sets the
+              number of milliseconds to wait between batches of rows
+              being processed by <literal>OPTIMIZE</literal>. The
+              default value is 10 milliseconds. It is possible to set a
+              lower value (to a minimum of <literal>0</literal>), but
+              not recommended. The maximum is 100000 milliseconds (that
+              is, 100 seconds).
             </para>
 
           </formalpara>


Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2008-01-09 16:10:01 UTC (rev 9530)
+++ trunk/refman-5.1/sql-syntax.xml	2008-01-09 16:25:45 UTC (rev 9531)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 1; 1028 bytes

@@ -17975,7 +17975,13 @@
           In MySQL 5.1.23-ndb-6.3.7 and later &mccge-series;
           6.3.<replaceable>x</replaceable> releases, <literal>OPTIMIZE
           TABLE</literal> is supported for dynamic columns of in-memory
-          <literal>NDB</literal> tables. See
+          <literal>NDB</literal> tables. The performance of
+          <literal>OPTIMIZE</literal> on Cluster tables can be tuned by
+          adjusting the value of the
+          <literal>ndb_optimization_delay</literal> system variable,
+          which controls the number of milliseconds to wait between
+          processing batches of rows by <literal>OPTIMIZE
+          TABLE</literal>. See
           <xref linkend="mysql-cluster-limitations-resolved"/>, for more
           information.
         </para>