Author: paul
Date: 2009-11-14 20:07:10 +0100 (Sat, 14 Nov 2009)
New Revision: 17598
Log:
r46399@frost: paul | 2009-11-14 12:14:09 -0500
Update changelog entry
Modified:
trunk/dynamic-docs/changelog/mysqld-1.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:27809
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:46395
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:27809
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:46399
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/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2009-11-14 02:55:18 UTC (rev 17597)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2009-11-14 19:07:10 UTC (rev 17598)
Changed blocks: 2, Lines Added: 27, Lines Deleted: 22; 3996 bytes
@@ -76619,20 +76619,23 @@
<message>
<para>
- In the default operation of the <literal role="se">InnoDB
- </literal> buffer pool, a block is loaded at the midpoint for
- the first access and then moved immediately to the head of the
- list as soon as another access occurs. In the case of a table
- scan (such as performed for a <command>mysqldump</command>
+ The <literal role="se">InnoDB </literal> buffer pool is divided
+ into two sublists: A new sublist containing blocks that are
+ heavily used by queries, and an old sublist containing less-used
+ blocks and from which candidates for eviction are taken. In the
+ default operation of the buffer pool, a block when read in is
+ loaded at the midpoint and then moved immediately to the head of
+ the new sublist as soon as an access occurs. In the case of a
+ table scan (such as performed for a <command>mysqldump</command>
operation), each block read by the scan ends up moving to the
- head of the list because multiple rows are accessed from each
- block. This occurs even for a one-time scan, where the blocks
- are not otherwise used by other queries. Blocks may also be
- loaded by the read-ahead background thread and then moved to the
- head of the new sublist by a single access. These effects are
- disadvantageous because they push blocks that are in heavy use
- by other queries out of the new sublist to the old sublist where
- they become subject to eviction.
+ head of the new sublist because multiple rows are accessed from
+ each block. This occurs even for a one-time scan, where the
+ blocks are not otherwise used by other queries. Blocks may also
+ be loaded by the read-ahead background thread and then moved to
+ the head of the new sublist by a single access. These effects
+ can be disadvantageous because they push blocks that are in
+ heavy use by other queries out of the new sublist to the old
+ sublist where they become subject to eviction.
</para>
<para>
@@ -76659,15 +76662,17 @@
</para>
<para>
Specifies how long in milliseconds (ms) a block inserted
- into the old sublist 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.
+ into the old sublist must stay there after its first access
+ before it can be moved to the new sublist. The default value
+ is 0: A block inserted into the old sublist moves
+ immediately to the new sublist the first time it is
+ accessed, no matter how soon after insertion the 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 the first access. For example, a value of 1000 causes
+ blocks to stay in the old sublist for 1 second after the
+ first access before they become eligible to move to the new
+ sublist. See <xref linkend="innodb-buffer-pool"/>
</para>
</listitem>
Modified: trunk/refman-5.5/se-innodb-core.xml
===================================================================
--- trunk/refman-5.5/se-innodb-core.xml 2009-11-14 02:55:18 UTC (rev 17597)
+++ trunk/refman-5.5/se-innodb-core.xml 2009-11-14 19:07:10 UTC (rev 17598)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 12; 2067 bytes
@@ -2308,18 +2308,18 @@
<para condition="dynamic:optvar:item" role="5.5:mysqld:innodb_old_blocks_time"/>
<para>
- (<literal>InnoDB Plugin</literal> only) Specifies how long in
- milliseconds (ms) a block inserted into the old sublist must
- stay there after its first access before it can be moved to
- the new sublist. The default value is 0: A block inserted into
- the old sublist moves immediately to the new sublist the first
- time it is accessed, no matter how soon after insertion the
- 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 the first access. For example, a value of 1000 causes
- blocks to stay in the old sublist for 1 second after the first
- access before they become eligible to move to the new sublist.
- See <xref linkend="innodb-buffer-pool"/>
+ Specifies how long in milliseconds (ms) a block inserted into
+ the old sublist must stay there after its first access before
+ it can be moved to the new sublist. The default value is 0: A
+ block inserted into the old sublist moves immediately to the
+ new sublist the first time it is accessed, no matter how soon
+ after insertion the 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 the first access. For
+ example, a value of 1000 causes blocks to stay in the old
+ sublist for 1 second after the first access before they become
+ eligible to move to the new sublist. See
+ <xref linkend="innodb-buffer-pool"/>
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r17598 - in trunk: . dynamic-docs/changelog refman-5.5 | paul.dubois | 14 Nov |
