svn commit - mysqldoc@oter02: r26303 - in trunk: . refman-5.6

[paul.dubois]

Author: pd221994
Date: 2011-05-20 20:44:37 +0200 (Fri, 20 May 2011)
New Revision: 26303

Log:


Modified:
   svk:merge
   trunk/refman-5.6/se-innodb-core.xml

Property changes on: trunk
___________________________________________________________________

Modified: svk:merge
===================================================================


Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 1277 bytes


Modified: trunk/refman-5.6/se-innodb-core.xml
===================================================================
--- trunk/refman-5.6/se-innodb-core.xml	2011-05-20 18:44:17 UTC (rev 26302)
+++ trunk/refman-5.6/se-innodb-core.xml	2011-05-20 18:44:37 UTC (rev 26303)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 7; 1272 bytes

@@ -10994,13 +10994,14 @@
           </para>
 
           <para>
-            The ability to raise the I/O limit should be especially
-            beneficial on platforms that support many IOPS. For example,
-            systems that use multiple disks or solid-state disks for
-            <literal>InnoDB</literal> are likely to benefit from the
-            ability to control this parameter. See
-            <xref linkend="innodb-performance-thread_io_rate"/> for more
-            information.
+            You can set the <literal>innodb_io_capacity</literal> value
+            to any number 100 or greater, and the default value is
+            <literal>200</literal>. You can set the value of this
+            parameter in the MySQL option file
+            (<literal>my.cnf</literal> or <literal>my.ini</literal>) or
+            change it dynamically with the <literal>SET GLOBAL</literal>
+            command, which requires the <literal>SUPER</literal>
+            privilege.
           </para>
 
           <para>