Author: mcbrown
Date: 2007-08-29 11:21:44 +0200 (Wed, 29 Aug 2007)
New Revision: 7574
Log:
Some rewording of the thread concurrency after further discussion with Ann/James/Brian.
Modified:
trunk/refman-5.0/se-innodb.xml
trunk/refman-5.1/se-innodb.xml
trunk/refman-5.2/se-innodb.xml
Modified: trunk/refman-5.0/se-innodb.xml
===================================================================
--- trunk/refman-5.0/se-innodb.xml 2007-08-29 02:26:01 UTC (rev 7573)
+++ trunk/refman-5.0/se-innodb.xml 2007-08-29 09:21:44 UTC (rev 7574)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 12; 1935 bytes
@@ -1104,9 +1104,10 @@
</para>
<para>
- The number of threads that can commit at the same time. A
- value of 0 disables concurrency control. This variable was
- added in MySQL 5.0.12.
+ The number of threads that can commit at the same time.
+ Setting this parameter to 0 allows any number of transactions
+ to commit simultaneously. This variable was added in MySQL
+ 5.0.12.
</para>
</listitem>
@@ -1760,20 +1761,18 @@
</para>
<para>
- As a general rule, the value of this setting should correspond
- with the CPU and disk count within your computer. Computers
- with high number of CPU cores and/or disks should increase
- this value to a value at least equal to the number of cores
- and disks in your system.
+ The correct value for this variable is dependent on
+ environment and workload. You will need to try a range
+ differnt values to determine what value works for your
+ application.
</para>
<para>
The range of this variable is 0 to 1000. A value of 20 or
higher is interpreted as infinite concurrency before MySQL
- 5.0.19. From 5.0.19 on, 0 is interpreted as infinite. Infinite
- means that concurrency checking is disabled and the possibly
- considerable overhead of acquiring and releasing a mutex is
- avoided.
+ 5.0.19. From 5.0.19 on, you can disable thread concurrency
+ checking by setting the value to 0, which allows InnoDB to
+ create as many threads as it needs.
</para>
<para>
Modified: trunk/refman-5.1/se-innodb.xml
===================================================================
--- trunk/refman-5.1/se-innodb.xml 2007-08-29 02:26:01 UTC (rev 7573)
+++ trunk/refman-5.1/se-innodb.xml 2007-08-29 09:21:44 UTC (rev 7574)
Changed blocks: 2, Lines Added: 10, Lines Deleted: 11; 1734 bytes
@@ -1104,8 +1104,9 @@
</para>
<para>
- The number of threads that can commit at the same time. A
- value of 0 disables concurrency control.
+ The number of threads that can commit at the same time.
+ Setting this parameter to 0 allows any number of transactions
+ to commit simultaneously.
</para>
</listitem>
@@ -1765,18 +1766,16 @@
</para>
<para>
- As a general rule, the value of this setting should correspond
- with the CPU and disk count within your computer. Computers
- with high number of CPU cores and/or disks should increase
- this value to a value at least equal to the number of cores
- and disks in your system.
+ The correct value for this variable is dependent on
+ environment and workload. You will need to try a range
+ differnt values to determine what value works for your
+ application.
</para>
<para>
- The range of this variable is 0 to 1000. You can disable
- thread concurrency checking by setting the value to 0. This
- disables the concurrency check and therefore allows InnoDB to
- create as many threads as it needs.
+ The range of this variable is 0 to 1000. you can disable
+ thread concurrency checking by setting the value to 0, which
+ allows InnoDB to create as many threads as it needs.
</para>
<para>
Modified: trunk/refman-5.2/se-innodb.xml
===================================================================
--- trunk/refman-5.2/se-innodb.xml 2007-08-29 02:26:01 UTC (rev 7573)
+++ trunk/refman-5.2/se-innodb.xml 2007-08-29 09:21:44 UTC (rev 7574)
Changed blocks: 2, Lines Added: 20, Lines Deleted: 15; 2544 bytes
@@ -1104,8 +1104,9 @@
</para>
<para>
- The number of threads that can commit at the same time. A
- value of 0 disables concurrency control.
+ The number of threads that can commit at the same time.
+ Setting this parameter to 0 allows any number of transactions
+ to commit simultaneously.
</para>
</listitem>
@@ -1757,21 +1758,25 @@
<literal>InnoDB</literal> tries to keep the number of
operating system threads concurrently inside
<literal>InnoDB</literal> less than or equal to the limit
- given by this variable. Once the number of threads reaches this limit,
- additional threads are placed into a wait state within a FIFO queue
- for execution. Threads waiting for locks are not counted in the number
- of concurrently executing threads.
+ given by this variable. Once the number of threads reaches
+ this limit, additional threads are placed into a wait state
+ within a FIFO queue for execution. Threads waiting for locks
+ are not counted in the number of concurrently executing
+ threads.
</para>
-
- <para>As a general rule, the value of this setting should correspond
- with the CPU and disk count within your computer. Computers with high
- number of CPU cores and/or disks should increase this value to a value
- at least equal to the number of cores and disks in your system. </para>
-
- <para>The range of this variable is 0 to 1000. You can disable thread concurrency checking by setting the value
- to 0. This disables the concurrency check and therefore allows
- InnoDB to create as many threads as it needs. </para>
+ <para>
+ The correct value for this variable is dependent on
+ environment and workload. You will need to try a range
+ differnt values to determine what value works for your
+ application.
+ </para>
+
+ <para>
+ The range of this variable is 0 to 1000. you can disable
+ thread concurrency checking by setting the value to 0, which
+ allows InnoDB to create as many threads as it needs.
+ </para>
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7574 - in trunk: refman-5.0 refman-5.1 refman-5.2 | mcbrown | 29 Aug |
