List:Commits« Previous MessageNext Message »
From:paul Date:January 10 2006 5:57pm
Subject:svn commit - mysqldoc@docsrva: r753 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2006-01-10 18:57:09 +0100 (Tue, 10 Jan 2006)
New Revision: 753

Log:
 r6054@frost:  paul | 2006-01-10 08:59:20 -0600
 Add units.


Modified:
   trunk/
   trunk/refman-4.1/innodb.xml
   trunk/refman-5.0/innodb.xml
   trunk/refman-5.1/innodb.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6053
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1994
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6054
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1994

Modified: trunk/refman-4.1/innodb.xml
===================================================================
--- trunk/refman-4.1/innodb.xml	2006-01-10 17:56:50 UTC (rev 752)
+++ trunk/refman-4.1/innodb.xml	2006-01-10 17:57:09 UTC (rev 753)
@@ -1080,10 +1080,10 @@
         </para>
 
         <para>
-          The size of a memory pool <literal>InnoDB</literal> uses to
-          store data dictionary information and other internal data
-          structures. The more tables you have in your application, the
-          more memory you need to allocate here. If
+          The size in bytes of a memory pool <literal>InnoDB</literal>
+          uses to store data dictionary information and other internal
+          data structures. The more tables you have in your application,
+          the more memory you need to allocate here. If
           <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
@@ -1097,7 +1097,7 @@
         </para>
 
         <para>
-          The increment size (in megabytes) for extending the size of an
+          The increment size (in MB) for extending the size of an
           auto-extending tablespace when it becomes full. The default
           value is 8. This option is available starting from MySQL
           4.0.24 and 4.1.5. As of MySQL 4.0.24 and 4.1.6, it can be
@@ -1139,13 +1139,14 @@
         </para>
 
         <para>
-          The size of the memory buffer <literal>InnoDB</literal> uses
-          to cache data and indexes of its tables. The larger you set
-          this value, the less disk I/O is needed to access data in
-          tables. On a dedicated database server, you may set this to up
-          to 80% of the machine physical memory size. However, do not
-          set it too large because competition for the physical memory
-          might cause paging in the operating system.
+          The size in bytes of the memory buffer
+          <literal>InnoDB</literal> uses to cache data and indexes of
+          its tables. The larger you set this value, the less disk I/O
+          is needed to access data in tables. On a dedicated database
+          server, you may set this to up to 80% of the machine physical
+          memory size. However, do not set it too large because
+          competition for the physical memory might cause paging in the
+          operating system.
         </para>
       </listitem>
 
@@ -1162,11 +1163,11 @@
           The paths to individual data files and their sizes. The full
           directory path to each data file is acquired by concatenating
           <literal>innodb_data_home_dir</literal> to each path specified
-          here. The file sizes are specified in megabytes or gigabytes
-          (1024MB) by appending <literal>M</literal> or
-          <literal>G</literal> to the size value. The sum of the sizes
-          of the files must be at least 10MB. On some operating systems,
-          files must be less than 2GB. If you do not specify
+          here. The file sizes are specified in MB or GB (1024MB) by
+          appending <literal>M</literal> or <literal>G</literal> to the
+          size value. The sum of the sizes of the files must be at least
+          10MB. On some operating systems, files must be less than 2GB.
+          If you do not specify
           <literal>innodb_data_file_path</literal>, the default behavior
           starting from 4.0 is to create a single 10MB auto-extending
           data file named <filename>ibdata1</filename>. Starting from
@@ -1456,11 +1457,11 @@
         </para>
 
         <para>
-          The size of the buffer that <literal>InnoDB</literal> uses to
-          write to the log files on disk. Sensible values range from 1MB
-          to 8MB. The default is 1MB. A large log buffer allows large
-          transactions to run without a need to write the log to disk
-          before the transactions commit. Thus, if you have big
+          The size in bytes of the buffer that <literal>InnoDB</literal>
+          uses to write to the log files on disk. Sensible values range
+          from 1MB to 8MB. The default is 1MB. A large log buffer allows
+          large transactions to run without a need to write the log to
+          disk before the transactions commit. Thus, if you have big
           transactions, making the log buffer larger saves disk I/O.
         </para>
       </listitem>
@@ -1471,10 +1472,10 @@
         </para>
 
         <para>
-          The size of each log file in a log group. The combined size of
-          log files must be less than 4GB on 32-bit computers. The
-          default is 5MB. Sensible values range from 1MB to
-          1/<replaceable>N</replaceable>-th of the size of the buffer
+          The size in bytes of each log file in a log group. The
+          combined size of log files must be less than 4GB on 32-bit
+          computers. The default is 5MB. Sensible values range from 1MB
+          to 1/<replaceable>N</replaceable>-th of the size of the buffer
           pool, where <replaceable>N</replaceable> is the number of log
           files in the group. The larger the value, the less checkpoint
           flush activity is needed in the buffer pool, saving disk I/O.
@@ -2861,9 +2862,9 @@
       the tablespace definition. Then <literal>InnoDB</literal>
       increases the size of that file automatically in 8MB increments
       when it runs out of space. Starting with MySQL 4.0.24 and 4.1.5,
-      the increment size can be configured with the option
-      <literal>innodb_autoextend_increment</literal>, in megabytes. The
-      default value is 8.
+      the increment size can be configured by setting the value of the
+      <literal>innodb_autoextend_increment</literal> system variable,
+      which is measured in MB, and has a default value of 8.
     </para>
 
     <para>

Modified: trunk/refman-5.0/innodb.xml
===================================================================
--- trunk/refman-5.0/innodb.xml	2006-01-10 17:56:50 UTC (rev 752)
+++ trunk/refman-5.0/innodb.xml	2006-01-10 17:57:09 UTC (rev 753)
@@ -961,10 +961,10 @@
         </para>
 
         <para>
-          The size of a memory pool <literal>InnoDB</literal> uses to
-          store data dictionary information and other internal data
-          structures. The more tables you have in your application, the
-          more memory you need to allocate here. If
+          The size in bytes of a memory pool <literal>InnoDB</literal>
+          uses to store data dictionary information and other internal
+          data structures. The more tables you have in your application,
+          the more memory you need to allocate here. If
           <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
@@ -978,7 +978,7 @@
         </para>
 
         <para>
-          The increment size (in megabytes) for extending the size of an
+          The increment size (in MB) for extending the size of an
           auto-extending tablespace when it becomes full. The default
           value is 8. This option can be changed at runtime as a global
           system variable.
@@ -1019,13 +1019,14 @@
         </para>
 
         <para>
-          The size of the memory buffer <literal>InnoDB</literal> uses
-          to cache data and indexes of its tables. The larger you set
-          this value, the less disk I/O is needed to access data in
-          tables. On a dedicated database server, you may set this to up
-          to 80% of the machine physical memory size. However, do not
-          set it too large because competition for the physical memory
-          might cause paging in the operating system.
+          The size in bytes of the memory buffer
+          <literal>InnoDB</literal> uses to cache data and indexes of
+          its tables. The larger you set this value, the less disk I/O
+          is needed to access data in tables. On a dedicated database
+          server, you may set this to up to 80% of the machine physical
+          memory size. However, do not set it too large because
+          competition for the physical memory might cause paging in the
+          operating system.
         </para>
       </listitem>
 
@@ -1091,11 +1092,11 @@
           The paths to individual data files and their sizes. The full
           directory path to each data file is acquired by concatenating
           <literal>innodb_data_home_dir</literal> to each path specified
-          here. The file sizes are specified in megabytes or gigabytes
-          (1024MB) by appending <literal>M</literal> or
-          <literal>G</literal> to the size value. The sum of the sizes
-          of the files must be at least 10MB. On some operating systems,
-          files must be less than 2GB. If you do not specify
+          here. The file sizes are specified in MB or GB (1024MB) by
+          appending <literal>M</literal> or <literal>G</literal> to the
+          size value. The sum of the sizes of the files must be at least
+          10MB. On some operating systems, files must be less than 2GB.
+          If you do not specify
           <literal>innodb_data_file_path</literal>, the default behavior
           starting is to create a single 10MB auto-extending data file
           named <filename>ibdata1</filename>. You can set the file size
@@ -1457,11 +1458,11 @@
         </para>
 
         <para>
-          The size of the buffer that <literal>InnoDB</literal> uses to
-          write to the log files on disk. Sensible values range from 1MB
-          to 8MB. The default is 1MB. A large log buffer allows large
-          transactions to run without a need to write the log to disk
-          before the transactions commit. Thus, if you have big
+          The size in bytes of the buffer that <literal>InnoDB</literal>
+          uses to write to the log files on disk. Sensible values range
+          from 1MB to 8MB. The default is 1MB. A large log buffer allows
+          large transactions to run without a need to write the log to
+          disk before the transactions commit. Thus, if you have big
           transactions, making the log buffer larger saves disk I/O.
         </para>
       </listitem>
@@ -1472,10 +1473,10 @@
         </para>
 
         <para>
-          The size of each log file in a log group. The combined size of
-          log files must be less than 4GB on 32-bit computers. The
-          default is 5MB. Sensible values range from 1MB to
-          1/<replaceable>N</replaceable>-th of the size of the buffer
+          The size in bytes of each log file in a log group. The
+          combined size of log files must be less than 4GB on 32-bit
+          computers. The default is 5MB. Sensible values range from 1MB
+          to 1/<replaceable>N</replaceable>-th of the size of the buffer
           pool, where <replaceable>N</replaceable> is the number of log
           files in the group. The larger the value, the less checkpoint
           flush activity is needed in the buffer pool, saving disk I/O.
@@ -2823,10 +2824,10 @@
       <literal>autoextend</literal> attribute for the last data file in
       the tablespace definition. Then <literal>InnoDB</literal>
       increases the size of that file automatically in 8MB increments
-      when it runs out of space. The increment size can be configured
-      setting the value of
-      <literal>innodb_autoextend_increment</literal>, which is measured
-      in megabytes,and whose default value is 8.
+      when it runs out of space. The increment size can be configured by
+      setting the value of the
+      <literal>innodb_autoextend_increment</literal> system variable,
+      which is measured in MB, and has a default value of 8.
     </para>
 
     <para>

Modified: trunk/refman-5.1/innodb.xml
===================================================================
--- trunk/refman-5.1/innodb.xml	2006-01-10 17:56:50 UTC (rev 752)
+++ trunk/refman-5.1/innodb.xml	2006-01-10 17:57:09 UTC (rev 753)
@@ -961,10 +961,10 @@
         </para>
 
         <para>
-          The size of a memory pool <literal>InnoDB</literal> uses to
-          store data dictionary information and other internal data
-          structures. The more tables you have in your application, the
-          more memory you need to allocate here. If
+          The size in bytes of a memory pool <literal>InnoDB</literal>
+          uses to store data dictionary information and other internal
+          data structures. The more tables you have in your application,
+          the more memory you need to allocate here. If
           <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
@@ -978,7 +978,7 @@
         </para>
 
         <para>
-          The increment size (in megabytes) for extending the size of an
+          The increment size (in MB) for extending the size of an
           auto-extending tablespace when it becomes full. The default
           value is 8. This option can be changed at runtime as a global
           system variable.
@@ -1020,13 +1020,14 @@
         </para>
 
         <para>
-          The size of the memory buffer <literal>InnoDB</literal> uses
-          to cache data and indexes of its tables. The larger you set
-          this value, the less disk I/O is needed to access data in
-          tables. On a dedicated database server, you may set this to up
-          to 80% of the machine physical memory size. However, do not
-          set it too large because competition for the physical memory
-          might cause paging in the operating system.
+          The size in bytes of the memory buffer
+          <literal>InnoDB</literal> uses to cache data and indexes of
+          its tables. The larger you set this value, the less disk I/O
+          is needed to access data in tables. On a dedicated database
+          server, you may set this to up to 80% of the machine physical
+          memory size. However, do not set it too large because
+          competition for the physical memory might cause paging in the
+          operating system.
         </para>
       </listitem>
 
@@ -1089,11 +1090,11 @@
           The paths to individual data files and their sizes. The full
           directory path to each data file is acquired by concatenating
           <literal>innodb_data_home_dir</literal> to each path specified
-          here. The file sizes are specified in megabytes or gigabytes
-          (1024MB) by appending <literal>M</literal> or
-          <literal>G</literal> to the size value. The sum of the sizes
-          of the files must be at least 10MB. On some operating systems,
-          files must be less than 2GB. If you do not specify
+          here. The file sizes are specified in MB or GB (1024MB) by
+          appending <literal>M</literal> or <literal>G</literal> to the
+          size value. The sum of the sizes of the files must be at least
+          10MB. On some operating systems, files must be less than 2GB.
+          If you do not specify
           <literal>innodb_data_file_path</literal>, the default behavior
           starting is to create a single 10MB auto-extending data file
           named <filename>ibdata1</filename>. You can set the file size
@@ -1450,11 +1451,11 @@
         </para>
 
         <para>
-          The size of the buffer that <literal>InnoDB</literal> uses to
-          write to the log files on disk. Sensible values range from 1MB
-          to 8MB. The default is 1MB. A large log buffer allows large
-          transactions to run without a need to write the log to disk
-          before the transactions commit. Thus, if you have big
+          The size in bytes of the buffer that <literal>InnoDB</literal>
+          uses to write to the log files on disk. Sensible values range
+          from 1MB to 8MB. The default is 1MB. A large log buffer allows
+          large transactions to run without a need to write the log to
+          disk before the transactions commit. Thus, if you have big
           transactions, making the log buffer larger saves disk I/O.
         </para>
       </listitem>
@@ -1465,10 +1466,10 @@
         </para>
 
         <para>
-          The size of each log file in a log group. The combined size of
-          log files must be less than 4GB on 32-bit computers. The
-          default is 5MB. Sensible values range from 1MB to
-          1/<replaceable>N</replaceable>-th of the size of the buffer
+          The size in bytes of each log file in a log group. The
+          combined size of log files must be less than 4GB on 32-bit
+          computers. The default is 5MB. Sensible values range from 1MB
+          to 1/<replaceable>N</replaceable>-th of the size of the buffer
           pool, where <replaceable>N</replaceable> is the number of log
           files in the group. The larger the value, the less checkpoint
           flush activity is needed in the buffer pool, saving disk I/O.
@@ -2799,10 +2800,10 @@
       <literal>autoextend</literal> attribute for the last data file in
       the tablespace definition. Then <literal>InnoDB</literal>
       increases the size of that file automatically in 8MB increments
-      when it runs out of space. The increment size can be configured
-      setting the value of
-      <literal>innodb_autoextend_increment</literal>, which is measured
-      in megabytes,and whose default value is 8.
+      when it runs out of space. The increment size can be configured by
+      setting the value of the
+      <literal>innodb_autoextend_increment</literal> system variable,
+      which is measured in MB, and has a default value of 8.
     </para>
 
     <para>

Thread
svn commit - mysqldoc@docsrva: r753 - in trunk: . refman-4.1 refman-5.0 refman-5.1paul10 Jan