Author: paul
Date: 2009-11-04 17:22:21 +0100 (Wed, 04 Nov 2009)
New Revision: 17441
Log:
r46100@frost: paul | 2009-11-04 10:14:38 -0500
Minor revisions, reformat
Modified:
trunk/refman-5.1/optimization.xml
trunk/refman-5.1/se-innodb-core.xml
trunk/refman-5.5/optimization.xml
trunk/refman-5.5/se-innodb-core.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:27523
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:25547
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:46087
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
+ 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:27523
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:25547
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:46100
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml 2009-11-04 15:34:08 UTC (rev 17440)
+++ trunk/refman-5.1/optimization.xml 2009-11-04 16:22:21 UTC (rev 17441)
Changed blocks: 3, Lines Added: 10, Lines Deleted: 9; 2507 bytes
@@ -10832,7 +10832,8 @@
greater than 0, blocks remain in the old sublist until an
access occurs at least that many ms after initial insertion.
For example, a value of 1000 causes blocks to stay in the
- old sublist for 1 second before moving to the new sublist.
+ old sublist for 1 second before they become eligible to move
+ to the new sublist.
</para>
</listitem>
@@ -10842,7 +10843,7 @@
<literal role="sysvar">innodb_old_blocks_pct</literal> and
<literal role="sysvar">innodb_old_blocks_time</literal> are
available as of MySQL 5.1.41, but only for <literal>InnoDB
- Plugin</literal>, not with the built-in version of
+ Plugin</literal>, not the built-in version of
<literal role="se">InnoDB</literal>.
</para>
@@ -10871,22 +10872,22 @@
<para>
<literal role="sysvar">innodb_old_blocks_time</literal> can be
set at runtime, so you can change it temporarily while
- performing an operation such as <command>mysqldump</command> to
- prevent table scans from flooding the new sublist:
+ performing an operation such as table scans and dumps to prevent
+ scans from flooding the new sublist:
</para>
<programlisting>
SET GLOBAL innodb_old_blocks_time = 1000;
-<replaceable>... perform mysqldump ...</replaceable>
+<replaceable>... perform queries that scan tables ...</replaceable>
SET GLOBAL innodb_old_blocks_time = 0;
</programlisting>
<para>
This strategy is unnecessary if your intent is to fill the
- buffer pool with a table's content. For example, if you perform
- a table or index scan at server startup or during benchmarking
- or testing specifically to <quote>warm up</quote> the buffer
- pool, leaving
+ buffer pool with a table's content. For example, you might
+ perform a table or index scan at server startup or during
+ benchmarking or testing specifically to <quote>warm up</quote>
+ the buffer pool. In this case, leaving
<literal role="sysvar">innodb_old_blocks_time</literal> set to 0
accomplishes the goal of loading the scanned blocks into the new
sublist.
Modified: trunk/refman-5.1/se-innodb-core.xml
===================================================================
--- trunk/refman-5.1/se-innodb-core.xml 2009-11-04 15:34:08 UTC (rev 17440)
+++ trunk/refman-5.1/se-innodb-core.xml 2009-11-04 16:22:21 UTC (rev 17441)
Changed blocks: 3, Lines Added: 44, Lines Deleted: 40; 5008 bytes
@@ -1517,7 +1517,8 @@
<literal>InnoDB</literal> runs out of memory in this pool, it
starts to allocate memory from the operating system and writes
warning messages to the MySQL error log. The default value is
- 1MB.
+ 1MB for the built-in <literal role="se">InnoDB</literal>, 8MB
+ for <literal>InnoDB Plugin</literal>.
</para>
</listitem>
@@ -1614,8 +1615,8 @@
the buffer pool is roughly proportional to its size. On large
installations, this initialization time may be significant.
For example, on a modern Linux x86_64 server, initialization
- of a 10GB buffer pool takes approximately 6 seconds.
- See <xref linkend="innodb-buffer-pool"/>
+ of a 10GB buffer pool takes approximately 6 seconds. See
+ <xref linkend="innodb-buffer-pool"/>
</para>
</listitem>
@@ -2546,51 +2547,54 @@
</para>
</listitem>
- <listitem>
- <para id="sysvar_innodb_old_blocks_pct">
- <literal role="sysvar">innodb_old_blocks_pct</literal>
- </para>
+ <listitem>
+ <para id="sysvar_innodb_old_blocks_pct">
+ <literal role="sysvar">innodb_old_blocks_pct</literal>
+ </para>
+
<para condition="dynamic:optvar:item" role="5.1:mysqld:innodb_old_blocks_pct"/>
- <para>
- (<literal>InnoDB Plugin</literal> only)
- Specifies the approximate percentage of the <literal role="se">InnoDB</literal> buffer pool used
- for the old block sublist. The range of values is 5 to 95.
- The default value is 37 (that is, 3/8 of the pool).
-See <xref linkend="innodb-buffer-pool"/>
- </para>
+ <para>
+ (<literal>InnoDB Plugin</literal> only) Specifies the
+ approximate percentage of the
+ <literal role="se">InnoDB</literal> buffer pool used for the
+ old block sublist. The range of values is 5 to 95. The default
+ value is 37 (that is, 3/8 of the pool). See
+ <xref linkend="innodb-buffer-pool"/>
+ </para>
-<para>
-This variable was added in MySQL 5.1.41.
-</para>
- </listitem>
+ <para>
+ This variable was added in MySQL 5.1.41.
+ </para>
+ </listitem>
- <listitem>
- <para id="sysvar_innodb_old_blocks_time">
- <literal role="sysvar">innodb_old_blocks_time</literal>
- </para>
+ <listitem>
+ <para id="sysvar_innodb_old_blocks_time">
+ <literal role="sysvar">innodb_old_blocks_time</literal>
+ </para>
<para condition="dynamic:optvar:item" role="5.1:mysqld:innodb_old_blocks_time"/>
- <para>
- (<literal>InnoDB Plugin</literal> only)
- Specifies how long in milliseconds (ms) a block inserted
- into the old sublist of the <literal role="se">InnoDB</literal> buffer pool must stay there before it can be moved
- to the new sublist. The default value is 0, so after a block
- is inserted into the old sublist, it moves immediately to
- the new sublist the next time it is accessed, no matter how
- soon after insertion the next access occurs. If the value is
- greater than 0, blocks remain in the old sublist until an
- access occurs at least that many ms after initial insertion.
- For example, a value of 1000 causes blocks to stay in the
- old sublist for 1 second before moving to the new sublist.
-See <xref linkend="innodb-buffer-pool"/>
- </para>
-<para>
-This variable was added in MySQL 5.1.41.
-</para>
- </listitem>
+ <para>
+ (<literal>InnoDB Plugin</literal> only) Specifies how long in
+ milliseconds (ms) a block inserted into the old sublist of the
+ <literal role="se">InnoDB</literal> buffer pool must stay
+ there before it can be moved to the new sublist. The default
+ value is 0, so after a block is inserted into the old sublist,
+ it moves immediately to the new sublist the next time it is
+ accessed, no matter how soon after insertion the next access
+ occurs. If the value is greater than 0, blocks remain in the
+ old sublist until an access occurs at least that many ms after
+ initial insertion. For example, a value of 1000 causes blocks
+ to stay in the old sublist for 1 second before moving to the
+ new sublist. See <xref linkend="innodb-buffer-pool"/>
+ </para>
+ <para>
+ This variable was added in MySQL 5.1.41.
+ </para>
+ </listitem>
+
<listitem>
<para id="sysvar_innodb_open_files">
<literal role="sysvar">innodb_open_files</literal>
Modified: trunk/refman-5.5/optimization.xml
===================================================================
--- trunk/refman-5.5/optimization.xml 2009-11-04 15:34:08 UTC (rev 17440)
+++ trunk/refman-5.5/optimization.xml 2009-11-04 16:22:21 UTC (rev 17441)
Changed blocks: 2, Lines Added: 9, Lines Deleted: 8; 2109 bytes
@@ -12137,7 +12137,8 @@
greater than 0, blocks remain in the old sublist until an
access occurs at least that many ms after initial insertion.
For example, a value of 1000 causes blocks to stay in the
- old sublist for 1 second before moving to the new sublist.
+ old sublist for 1 second before they become eligible to move
+ to the new sublist.
</para>
</listitem>
@@ -12168,22 +12169,22 @@
<para>
<literal role="sysvar">innodb_old_blocks_time</literal> can be
set at runtime, so you can change it temporarily while
- performing an operation such as <command>mysqldump</command> to
- prevent table scans from flooding the new sublist:
+ performing an operation such as table scans and dumps to prevent
+ scans from flooding the new sublist:
</para>
<programlisting>
SET GLOBAL innodb_old_blocks_time = 1000;
-<replaceable>... perform mysqldump ...</replaceable>
+<replaceable>... perform queries that scan tables ...</replaceable>
SET GLOBAL innodb_old_blocks_time = 0;
</programlisting>
<para>
This strategy is unnecessary if your intent is to fill the
- buffer pool with a table's content. For example, if you perform
- a table or index scan at server startup or during benchmarking
- or testing specifically to <quote>warm up</quote> the buffer
- pool, leaving
+ buffer pool with a table's content. For example, you might
+ perform a table or index scan at server startup or during
+ benchmarking or testing specifically to <quote>warm up</quote>
+ the buffer pool. In this case, leaving
<literal role="sysvar">innodb_old_blocks_time</literal> set to 0
accomplishes the goal of loading the scanned blocks into the new
sublist.
Modified: trunk/refman-5.5/se-innodb-core.xml
===================================================================
--- trunk/refman-5.5/se-innodb-core.xml 2009-11-04 15:34:08 UTC (rev 17440)
+++ trunk/refman-5.5/se-innodb-core.xml 2009-11-04 16:22:21 UTC (rev 17441)
Changed blocks: 2, Lines Added: 33, Lines Deleted: 31; 3969 bytes
@@ -1436,8 +1436,7 @@
size. On large installations, this initialization time may be
significant. For example, on a modern Linux x86_64 server,
initialization of a 10GB buffer pool takes approximately 6
- seconds.
-See <xref linkend="innodb-buffer-pool"/>
+ seconds. See <xref linkend="innodb-buffer-pool"/>
</para>
</listitem>
@@ -2285,41 +2284,44 @@
</para>
</listitem>
- <listitem>
- <para id="sysvar_innodb_old_blocks_pct">
- <literal role="sysvar">innodb_old_blocks_pct</literal>
- </para>
+ <listitem>
+ <para id="sysvar_innodb_old_blocks_pct">
+ <literal role="sysvar">innodb_old_blocks_pct</literal>
+ </para>
+
<para condition="dynamic:optvar:item" role="5.5:mysqld:innodb_old_blocks_pct"/>
- <para>
- Specifies the approximate percentage of the <literal role="se">InnoDB</literal> buffer pool used
- for the old block sublist. The range of values is 5 to 95.
- The default value is 37 (that is, 3/8 of the pool).
-See <xref linkend="innodb-buffer-pool"/>
- </para>
- </listitem>
+ <para>
+ Specifies the approximate percentage of the
+ <literal role="se">InnoDB</literal> buffer pool used for the
+ old block sublist. The range of values is 5 to 95. The default
+ value is 37 (that is, 3/8 of the pool). See
+ <xref linkend="innodb-buffer-pool"/>
+ </para>
+ </listitem>
- <listitem>
- <para id="sysvar_innodb_old_blocks_time">
- <literal role="sysvar">innodb_old_blocks_time</literal>
- </para>
+ <listitem>
+ <para id="sysvar_innodb_old_blocks_time">
+ <literal role="sysvar">innodb_old_blocks_time</literal>
+ </para>
<para condition="dynamic:optvar:item" role="5.5:mysqld:innodb_old_blocks_time"/>
- <para>
- Specifies how long in milliseconds (ms) a block inserted
- into the old sublist of the <literal role="se">InnoDB</literal> buffer pool must stay there before it can be moved
- to the new sublist. The default value is 0, so after a block
- is inserted into the old sublist, it moves immediately to
- the new sublist the next time it is accessed, no matter how
- soon after insertion the next access occurs. If the value is
- greater than 0, blocks remain in the old sublist until an
- access occurs at least that many ms after initial insertion.
- For example, a value of 1000 causes blocks to stay in the
- old sublist for 1 second before moving to the new sublist.
-See <xref linkend="innodb-buffer-pool"/>
- </para>
- </listitem>
+ <para>
+ Specifies how long in milliseconds (ms) a block inserted into
+ the old sublist of the <literal role="se">InnoDB</literal>
+ buffer pool must stay there before it can be moved to the new
+ sublist. The default value is 0, so after a block is inserted
+ into the old sublist, it moves immediately to the new sublist
+ the next time it is accessed, no matter how soon after
+ insertion the next access occurs. If the value is greater than
+ 0, blocks remain in the old sublist until an access occurs at
+ least that many ms after initial insertion. For example, a
+ value of 1000 causes blocks to stay in the old sublist for 1
+ second before moving to the new sublist. See
+ <xref linkend="innodb-buffer-pool"/>
+ </para>
+ </listitem>
<listitem>
<para id="sysvar_innodb_open_files">
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r17441 - in trunk: . refman-5.1 refman-5.5 | paul.dubois | 4 Nov |
