List:Commits« Previous MessageNext Message »
From:john.russell Date:March 28 2011 7:54pm
Subject:svn commit - mysqldoc@oter02: r25595 - trunk/innodb-1.1
View as plain text  
Author: jdrussel
Date: 2011-03-28 21:54:58 +0200 (Mon, 28 Mar 2011)
New Revision: 25595

Log:
Commenting out, not a 5.5 item.


Modified:
   trunk/innodb-1.1/innodb-performance.xml


Modified: trunk/innodb-1.1/innodb-performance.xml
===================================================================
--- trunk/innodb-1.1/innodb-performance.xml	2011-03-28 19:37:33 UTC (rev 25594)
+++ trunk/innodb-1.1/innodb-performance.xml	2011-03-28 19:54:58 UTC (rev 25595)
Changed blocks: 4, Lines Added: 20, Lines Deleted: 8; 2594 bytes

@@ -1697,6 +1697,9 @@
 
   </section>
 
+<!-- JDR: decide whether to group new ones like metrics with like items, or put in chronological or reverse-" order. -->
+
+<!--
   <section id="innodb-metrics-counters">
 
     <title>InnoDB Metrics Counters</title>

@@ -1714,10 +1717,12 @@
       same optimized techniques to avoid performance overhead as the
       other InnoDB <literal>information_schema</literal> tables.
     </para>
+-->
 
 <!-- JDR: try out the links to see what the best order and division is
 for these cross-references. -->
 
+<!--
     <para>
       For usage information on InnoDB-related
       <literal>information_schema</literal> tables, see

@@ -1729,6 +1734,7 @@
     </para>
 
   </section>
+-->
 
   <section id="innodb-multiple-buffer-pools">
 

@@ -1790,15 +1796,21 @@
     </indexterm>
 
     <para>
-      The InnoDB <link linkend="glos_rollback_segment">rollback
-      segment</link> could be a bottleneck on high-capacity systems,
-      because it can handle a maximum of 1023 concurrent transactions
-      that change any data. (Read-only transactions do not count against
-      that maximum.) Starting in InnoDB 1.1 with MySQL 5.5, the limit on
-      concurrent transactions is greatly expanded. The single rollback
-      segment is divided into 128 segments, each of which can support up
+      Starting in InnoDB 1.1 with MySQL 5.5, the limit on
+      concurrent <link linkend="glos_transaction">transactions</link> is greatly expanded,
+      removing a bottleneck with the InnoDB <link linkend="glos_rollback_segment">rollback
+      segment</link> that affected high-capacity systems,
+      because
+      The limit applies to concurrent transactions
+      that change any data.
+      (Read-only transactions do not count against
+      that maximum.)
+      The single rollback
+      segment is now divided into 128 segments, each of which can support up
       to 1023 transactions that perform writes, for a total of
-      approximately 128K concurrent transactions. Each transaction is
+      approximately 128K concurrent transactions.
+      The original transaction limit was 1023.
+      Each transaction is
       assigned to one of the rollback segments, and remains tied to that
       rollback segment for the duration. This enhancement improves both
       scalability (higher number of concurrent transactions) and


Thread
svn commit - mysqldoc@oter02: r25595 - trunk/innodb-1.1john.russell28 Mar