svn commit - mysqldoc@docsrva: r346 - in trunk: . refman-4.1 refman-5.0 refman-5.1

[paul]

Author: paul
Date: 2005-11-16 17:31:24 +0100 (Wed, 16 Nov 2005)
New Revision: 346

Log:
 r3790@frost:  paul | 2005-11-16 10:28:51 -0600
 Additional info about InnoDB on Solaris.


Modified:
   trunk/
   trunk/refman-4.1/innodb.xml
   trunk/refman-5.0/innodb.xml
   trunk/refman-5.1/innodb.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:3733
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1036
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:3790
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1036

Modified: trunk/refman-4.1/innodb.xml
===================================================================
--- trunk/refman-4.1/innodb.xml	2005-11-15 21:05:57 UTC (rev 345)
+++ trunk/refman-4.1/innodb.xml	2005-11-16 16:31:24 UTC (rev 346)
@@ -4719,6 +4719,26 @@
           degradation of InnoDB's speed and performance on this
           platform.
         </para>
+
+        <para>
+          When using the <literal>InnoDB</literal> storage engine with a
+          large <literal>innodb_buffer_pool_size</literal> value on any
+          release Solaris &ge; 2.6 and any platform
+          (sparc/x86/x64/amd64), a significant performance gain can be
+          achieved by placing <literal>InnoDB</literal> data files and
+          log files on raw devices or on a seperate direct I/O UFS
+          Filesystem (mount option <literal>forcedirectio</literal>; see
+          <literal>mount_ufs(1M)</literal>). Users of the Veritas
+          filesystem VxFS should use the mount option
+          <literal>convosync=direct</literal>.
+        </para>
+
+        <para>
+          Other MySQL data files such as those for
+          <literal>MyISAM</literal> tables should not be placed on a
+          direct I/O filesystem. Executables or libraries <emphasis>must
+          not</emphasis> be placed on a direct I/O filesystem.
+        </para>
       </listitem>
 
       <listitem>

Modified: trunk/refman-5.0/innodb.xml
===================================================================
--- trunk/refman-5.0/innodb.xml	2005-11-15 21:05:57 UTC (rev 345)
+++ trunk/refman-5.0/innodb.xml	2005-11-16 16:31:24 UTC (rev 346)
@@ -112,7 +112,9 @@
 
     <para>
       <emphasis role="bold">Additional resources</emphasis>
+
       <itemizedlist>
+
         <listitem>
           <para>
             For the <literal>InnoDB</literal> storage engine, there's a
@@ -120,9 +122,10 @@
             <ulink url="http://forums.mysql.com/list.php?22"/>.
           </para>
         </listitem>
+
       </itemizedlist>
     </para>
-    
+
   </section>
 
   <section id="innodb-contact-information">
@@ -4636,6 +4639,26 @@
           degradation of InnoDB's speed and performance on this
           platform.
         </para>
+
+        <para>
+          When using the <literal>InnoDB</literal> storage engine with a
+          large <literal>innodb_buffer_pool_size</literal> value on any
+          release Solaris &ge; 2.6 and any platform
+          (sparc/x86/x64/amd64), a significant performance gain can be
+          achieved by placing <literal>InnoDB</literal> data files and
+          log files on raw devices or on a seperate direct I/O UFS
+          Filesystem (mount option <literal>forcedirectio</literal>; see
+          <literal>mount_ufs(1M)</literal>). Users of the Veritas
+          filesystem VxFS should use the mount option
+          <literal>convosync=direct</literal>.
+        </para>
+
+        <para>
+          Other MySQL data files such as those for
+          <literal>MyISAM</literal> tables should not be placed on a
+          direct I/O filesystem. Executables or libraries <emphasis>must
+          not</emphasis> be placed on a direct I/O filesystem.
+        </para>
       </listitem>
 
       <listitem>

Modified: trunk/refman-5.1/innodb.xml
===================================================================
--- trunk/refman-5.1/innodb.xml	2005-11-15 21:05:57 UTC (rev 345)
+++ trunk/refman-5.1/innodb.xml	2005-11-16 16:31:24 UTC (rev 346)
@@ -112,7 +112,9 @@
 
     <para>
       <emphasis role="bold">Additional resources</emphasis>
+
       <itemizedlist>
+
         <listitem>
           <para>
             For the <literal>InnoDB</literal> storage engine, there's a
@@ -120,6 +122,7 @@
             <ulink url="http://forums.mysql.com/list.php?22"/>.
           </para>
         </listitem>
+
       </itemizedlist>
     </para>
 
@@ -4597,6 +4600,26 @@
           degradation of InnoDB's speed and performance on this
           platform.
         </para>
+
+        <para>
+          When using the <literal>InnoDB</literal> storage engine with a
+          large <literal>innodb_buffer_pool_size</literal> value on any
+          release Solaris &ge; 2.6 and any platform
+          (sparc/x86/x64/amd64), a significant performance gain can be
+          achieved by placing <literal>InnoDB</literal> data files and
+          log files on raw devices or on a seperate direct I/O UFS
+          Filesystem (mount option <literal>forcedirectio</literal>; see
+          <literal>mount_ufs(1M)</literal>). Users of the Veritas
+          filesystem VxFS should use the mount option
+          <literal>convosync=direct</literal>.
+        </para>
+
+        <para>
+          Other MySQL data files such as those for
+          <literal>MyISAM</literal> tables should not be placed on a
+          direct I/O filesystem. Executables or libraries <emphasis>must
+          not</emphasis> be placed on a direct I/O filesystem.
+        </para>
       </listitem>
 
       <listitem>