bk commit - mysqldoc@docsrva tree (marko:1.2898)

[Marko Mäkelä]

Below is the list of changes that have just been committed into a local
mysqldoc repository of marko. When marko does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2898 05/06/28 16:43:33 marko@stripped +1 -0
  news.xml:
    news-5-0-9, news-4-1-13: Describe the performance fix for extending
    InnoDB data files

  refman/news.xml
    1.36 05/06/28 16:42:38 marko@stripped +19 -1
    news-5-0-9, news-4-1-13: Describe the performance fix for extending
    InnoDB data files

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	marko
# Host:	hundin.mysql.fi
# Root:	/home/marko/k/mysqldoc

--- 1.35/refman/news.xml	Fri Jun 24 20:41:11 2005
+++ 1.36/refman/news.xml	Tue Jun 28 16:42:38 2005
@@ -215,7 +215,15 @@
 
    <itemizedlist>
 
-    <listitem><para></para></listitem>
+    <listitem><para>
+     <literal>InnoDB</literal>: When creating or extending an InnoDB
+     data file, allocate at most one megabyte at a time for initializing
+     the file.  Previously, InnoDB used to allocate and initialize
+     1 or 8 megabytes of memory, even if a few 16-kilobyte pages were to
+     be written.  This fix improves the performance of
+     <literal>CREATE TABLE</literal> in
+     <literal>innodb_file_per_table</literal> mode.
+    </para></listitem>
 
    </itemizedlist>
 
@@ -4658,6 +4666,16 @@
     <listitem><para>
      <literal>InnoDB</literal>: Make <literal>CHECK
TABLE</literal>
      killable. (Bug #9730)
+    </para></listitem>
+
+    <listitem><para>
+     <literal>InnoDB</literal>: When creating or extending an InnoDB
+     data file, allocate at most one megabyte at a time for initializing
+     the file.  Previously, InnoDB used to allocate and initialize
+     1 or 8 megabytes of memory, even if a few 16-kilobyte pages were to
+     be written.  This fix improves the performance of
+     <literal>CREATE TABLE</literal> in
+     <literal>innodb_file_per_table</literal> mode.
     </para></listitem>
 
    </itemizedlist>