List:Commits« Previous MessageNext Message »
From:john.russell Date:April 21 2011 12:12am
Subject:svn commit - mysqldoc@oter02: r25950 - trunk/dynamic-docs/glossary
View as plain text  
Author: jdrussel
Date: 2011-04-21 02:12:10 +0200 (Thu, 21 Apr 2011)
New Revision: 25950

Log:
Adding a bunch of terms needed to understand varied configurations such as
replication slaves with multiple instances.


Modified:
   trunk/dynamic-docs/glossary/innodb.xml


Modified: trunk/dynamic-docs/glossary/innodb.xml
===================================================================
--- trunk/dynamic-docs/glossary/innodb.xml	2011-04-20 23:37:01 UTC (rev 25949)
+++ trunk/dynamic-docs/glossary/innodb.xml	2011-04-21 00:12:10 UTC (rev 25950)
Changed blocks: 8, Lines Added: 120, Lines Deleted: 40; 7406 bytes

@@ -1481,6 +1481,27 @@
 
   </glossent>
 
+  <glossent id="cpu_bound">
+
+    <gterm>disk-bound</gterm>
+    <def>
+
+      <para>
+        A type of <emphasis role="bold">workload</emphasis> where the
+        primary <emphasis role="bold">bottleneck</emphasis> is CPU
+        operations in memory. Typically involves read-intensive
+        operations where the results can all be cached in the
+        <emphasis role="bold">buffer pool</emphasis>.
+      </para>
+
+    </def>
+    <gseealso glosid="workload"/>
+    <gseealso glosid="cpu_bound"/>
+    <gseealso glosid="bottleneck"/>
+    <gseealso glosid="buffer_pool"/>
+
+  </glossent>
+
   <glossent id="crash_recovery">
 
     <gterm>crash recovery</gterm>

@@ -1873,30 +1894,6 @@
 
   </glossent>
 
-  <glossent id="disk_based">
-
-    <gterm>disk-based</gterm>
-    <def>
-
-      <para>
-        A kind of database that primarily organizes data on disk storage
-        (hard drives or equivalent). Data is brought back and forth
-        between disk and memory to be operated upon. It is the opposite
-        of an <emphasis role="bold">in-memory database</emphasis>.
-        Although InnoDB is disk-based, it also contains features such as
-        <emphasis role="bold">the buffer</emphasis> pool, multiple
-        buffer pool instances, and the <emphasis role="bold">adaptive
-        hash index</emphasis> that allow certain kinds of workloads to
-        work primarily from memory.
-      </para>
-
-    </def>
-    <gseealso glosid="in_memory_database"/>
-    <gseealso glosid="buffer_pool"/>
-    <gseealso glosid="adaptive_hash_index"/>
-
-  </glossent>
-
   <glossent id="data_files">
 
     <gterm>data files</gterm>

@@ -2029,6 +2026,51 @@
 
   </glossent>
 
+  <glossent id="disk_based">
+
+    <gterm>disk-based</gterm>
+    <def>
+
+      <para>
+        A kind of database that primarily organizes data on disk storage
+        (hard drives or equivalent). Data is brought back and forth
+        between disk and memory to be operated upon. It is the opposite
+        of an <emphasis role="bold">in-memory database</emphasis>.
+        Although InnoDB is disk-based, it also contains features such as
+        <emphasis role="bold">the buffer</emphasis> pool, multiple
+        buffer pool instances, and the <emphasis role="bold">adaptive
+        hash index</emphasis> that allow certain kinds of workloads to
+        work primarily from memory.
+      </para>
+
+    </def>
+    <gseealso glosid="in_memory_database"/>
+    <gseealso glosid="buffer_pool"/>
+    <gseealso glosid="adaptive_hash_index"/>
+
+  </glossent>
+
+  <glossent id="disk_bound">
+
+    <gterm>disk-bound</gterm>
+    <def>
+
+      <para>
+        A type of <emphasis role="bold">workload</emphasis> where the
+        primary <emphasis role="bold">bottleneck</emphasis> is disk I/O.
+        Typically involves frequent writes to disk, or random reads of
+        more data than can fit into the <emphasis role="bold">buffer
+        pool</emphasis>.
+      </para>
+
+    </def>
+    <gseealso glosid="workload"/>
+    <gseealso glosid="cpu_bound"/>
+    <gseealso glosid="bottleneck"/>
+    <gseealso glosid="buffer_pool"/>
+
+  </glossent>
+
   <glossent id="early_adopter">
 
     <gterm>early adopter</gterm>

@@ -3458,6 +3500,34 @@
 
   </glossent>
 
+  <glossent id="instance">
+
+    <gterm>instance</gterm>
+    <def>
+
+      <para>
+        A single <emphasis role="bold">mysqld</emphasis> daemon managing
+        a data directory representing one or more
+        <emphasis role="bold">databases</emphasis> with a set of
+        <emphasis role="bold">tables</emphasis>. It is common in
+        development, testing, and some
+        <emphasis role="bold">replication</emphasis> scenarios to have
+        multiple instances on the same server machine, each managing its
+        own data directory and listening on its own port or socket. With
+        one instance running a
+        <emphasis role="bold">disk-bound</emphasis> workload, the server
+        might still have extra CPU and memory capacity to run additional
+        instances.
+      </para>
+
+    </def>
+    <gseealso glosid="mysqld"/>
+    <gseealso glosid="database"/>
+    <gseealso glosid="replication"/>
+    <gseealso glosid="disk_bound"/>
+
+  </glossent>
+
   <glossent id="instrumentation">
 
     <gterm>instrumentation</gterm>

@@ -3990,22 +4060,23 @@
 
   </glossent>
 
-  <glossent id="master_database">
+  <glossent id="master_server">
 
-    <gterm>master database</gterm>
+    <gterm>master server</gterm>
     <def>
 
       <para>
-        In a <emphasis role="bold">replication</emphasis> scenario, the
-        database that processes the initial insert, update, and delete
+        Frequently shortened to <quote>master</quote>. A database server
+        machine in a <emphasis role="bold">replication</emphasis>
+        scenario that processes the initial insert, update, and delete
         requests for data. These changes are propagated to, and repeated
-        on, other databases known as <emphasis role="bold">slave
-        databases</emphasis>.
+        on, other servers known as <emphasis role="bold">slave
+        servers</emphasis>.
       </para>
 
     </def>
     <gseealso glosid="replication"/>
-    <gseealso glosid="slave_database"/>
+    <gseealso glosid="slave_server"/>
 
   </glossent>
 

@@ -6239,19 +6310,18 @@
 
   </glossent>
 
-  <glossent id="slave_database">
+  <glossent id="slave_server">
 
-    <gterm>slave database</gterm>
+    <gterm>slave server</gterm>
     <def>
 
       <para>
-        A <emphasis role="bold">slave database</emphasis>, frequently
-        shortened to <quote>slave</quote>, is a database in a
-        <emphasis role="bold">replication</emphasis> scenario that
-        receives changes from another database (the
-        <emphasis role="bold">master database</emphasis>) and applies
-        those same changes. Thus it maintains the same contents as the
-        master, although it might lag somewhat behind.
+        Frequently shortened to <quote>slave</quote>. A database server
+        machine in a <emphasis role="bold">replication</emphasis>
+        scenario that receives changes from another server (the
+        <emphasis role="bold">master</emphasis>) and applies those same
+        changes. Thus it maintains the same contents as the master,
+        although it might lag somewhat behind.
       </para>
       <para>
         In MySQL, slave databases are commonly used in disaster

@@ -6260,6 +6330,14 @@
         new settings, to ensure that database configuration changes do
         not cause problems with performance or reliability.
       </para>
+      <para>
+        To ensure that slave servers can apply changes from the master
+        fast enough, they frequently have fast I/O devices and
+        sufficient CPU and memory to run multiple database instances on
+        the same slave server. For example, the master server might use
+        hard drive storage while the slave servers use
+        <emphasis role="bold">SSD</emphasis>s.
+      </para>
 
     </def>
     <gseealso glosid="replication"/>

@@ -7353,6 +7431,8 @@
     </def>
     <gseealso glosid="sql"/>
     <gseealso glosid="bottleneck"/>
+    <gseealso glosid="disk_bound"/>
+    <gseealso glosid="cpu_bound"/>
 
   </glossent>
 


Thread
svn commit - mysqldoc@oter02: r25950 - trunk/dynamic-docs/glossaryjohn.russell21 Apr