Author: plavin
Date: 2007-02-02 19:15:15 +0100 (Fri, 02 Feb 2007)
New Revision: 4765
Log:
Copy over MNMAS ads
Modified:
trunk/refman-5.1/optimization.xml
Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml 2007-02-02 18:05:54 UTC (rev 4764)
+++ trunk/refman-5.1/optimization.xml 2007-02-02 18:15:15 UTC (rev 4765)
Changed blocks: 10, Lines Added: 102, Lines Deleted: 0; 6397 bytes
@@ -2026,6 +2026,15 @@
clause.
</para>
+ <formalpara role="mnmas">
+ <title>MySQL Enterprise</title>
+ <para>
+ Subscribers to the MySQL Network Monitoring and Advisory Service
+ regularly receive expert advice on optimization. For more information
+ see, <ulink url="&base-url-enterprise;advisors.html"/>.
+ </para>
+ </formalpara>
+
</section>
<section id="estimating-performance">
@@ -5505,6 +5514,16 @@
</itemizedlist>
+ <formalpara role="mnmas">
+ <title>MySQL Enterprise</title>
+ <para>
+ For more advice on optimizing the performance of your server,
+ subscribe to the MySQL Network Monitoring and Advisory Service.
+ Numerous advisors are dedicated to monitoring performance.
+ For more information see, <ulink url="&base-url-enterprise;advisors.html"/>.
+ </para>
+ </formalpara>
+
</section>
<section id="update-speed">
@@ -6032,6 +6051,15 @@
<literal>MyISAM</literal> setup is very well tuned for this.
</para>
+ <formalpara role="mnmas">
+ <title>MySQL Enterprise</title>
+ <para>
+ The MySQL Network Monitoring and Advisory Service provides
+ expert advice on when to use table-level and when to use
+ row-level locking. To subscribe see, <ulink url="&base-url-enterprise;advisors.html" />.
+ </para>
+ </formalpara>
+
<para>
Table locking in MySQL is deadlock-free for storage engines that
use table-level locking. Deadlock avoidance is managed by always
@@ -6549,6 +6577,17 @@
your tables to <literal>InnoDB</literal>. See
<xref linkend="innodb"/>.
</para>
+
+ <formalpara role="mnmas">
+ <title>MySQL Enterprise</title>
+ <para>
+ Lock contention can seriously degrade performance.
+ The MySQL Network Monitoring and Advisory Service provides
+ expert advice on avoiding this problem.
+ To subscribe see, <ulink url="&base-url-enterprise;advisors.html" />.
+ </para>
+ </formalpara>
+
</listitem>
</itemizedlist>
@@ -7449,6 +7488,18 @@
</itemizedlist>
+
+ <formalpara role="mnmas">
+ <title>MySQL Enterprise</title>
+ <para>
+ Often, it is not possible to predict exactly what indexes will be required
+ or will be most efficient — actual table usage is the best indicator.
+ The MySQL Network Monitoring and Advisory Service
+ provides expert advice on this topic. For more information see,
+ <ulink url="base-url-enterprise;advisors.html"/>.
+ </para>
+ </formalpara>
+
</section>
<section id="myisam-key-cache">
@@ -7525,6 +7576,16 @@
buffers (8).
</para>
+ <formalpara role="mnmas">
+ <title>MySQL Enterprise</title>
+ <para>
+ For expert advice on identifying the optimum size for
+ <literal>key_buffer_size</literal>, subscribe to the
+ MySQL Network Monitoring and Advisory Service. See
+ <ulink url="&base-url-enterprise;advisors.html"/>.
+ </para>
+ </formalpara>
+
<para>
When the key cache is not operational, index files are accessed
using only the native filesystem buffering provided by the
@@ -7812,6 +7873,16 @@
init_file=/<replaceable>path</replaceable>/<replaceable>to</replaceable>/<replaceable>data-directory</replaceable>/mysqld_init.sql
</programlisting>
+ <formalpara role="mnmas">
+ <title>MySQL Enterprise</title>
+ <para>
+ For advice on how best to configure your <filename>my.cnf/my.ini </filename>
+ option file subscribe to MySQL Network Monitoring and Advisory Service.
+ Recommendations are based on actual table usage. For more information
+ see, <ulink url="&base-url-enterprise;advisors.html"/>.
+ </para>
+ </formalpara>
+
<para>
The statements in <filename>mysqld_init.sql</filename> are
executed each time the server starts. The file should contain
@@ -8421,6 +8492,16 @@
more tables than this to execute queries.
</para>
+ <formalpara role="mnmas">
+ <title>MySQL Enterprise</title>
+ <para>
+ Performance may suffer if <literal>table_cache</literal> is set too
+ low. For expert advice on the optimum value for this variable,
+ subscribe to the MySQL Network Monitoring and Advisory Service.
+ For more information see, <ulink url="&base-url-enterprise;advisors.html"/>.
+ </para>
+ </formalpara>
+
<para>
MySQL closes an unused table and removes it from the table cache
under the following circumstances:
@@ -9131,6 +9212,14 @@
engine, see <xref linkend="innodb-tuning"/>.
</para>
+ <formalpara role="mnmas">
+ <title>MySQL Enterprise</title>
+ <para>
+ For expert advice on tuning system parameters subscribe to the
+ MySQL Network Monitoring and Advisory Service. For more information see,
+ <ulink url="&base-url-enterprise;advisors.html"/>.
+ </para>
+ </formalpara>
</section>
<section id="controlling-optimizer">
@@ -9560,6 +9649,19 @@
<literal>SQL_BIG_TABLES</literal> in the client program. See
<xref linkend="set-option"/>.
</para>
+
+ <formalpara role="mnmas">
+ <title>MySQL Enterprise</title>
+ <para>
+ Subscribers to the MySQL Network Monitoring and Advisory Service are
+ alerted when temporary tables exceed <literal>tmp_table_size</literal>. Advisors make
+ recommendations for the optimum value of <literal>tmp_table_size</literal> based on
+ actual table usage. For more information about the MySQL Network Monitoring and
+ Advisory Service please see,
+ <ulink url="&base-url-enterprise;advisors.html" />.
+ </para>
+ </formalpara>
+
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4765 - trunk/refman-5.1 | plavin | 2 Feb |
