Author: plavin
Date: 2006-08-30 17:20:43 +0200 (Wed, 30 Aug 2006)
New Revision: 3146
Log:
Update health chapter
Modified:
trunk/administrator/health.xml
Modified: trunk/administrator/health.xml
===================================================================
--- trunk/administrator/health.xml 2006-08-30 14:28:35 UTC (rev 3145)
+++ trunk/administrator/health.xml 2006-08-30 15:20:43 UTC (rev 3146)
Changed blocks: 14, Lines Added: 21, Lines Deleted: 21; 7584 bytes
@@ -14,8 +14,8 @@
<title>Introduction</title>
<para>
- The <literal>Health</literal> section of &administrator; allows
- you to graphically monitor the real-time status of your MySQL
+ The <literal>Health</literal> section of &administrator; shows
+ you how to graphically monitor the real-time status of your MySQL
server. A selection of pre-made status graphs are available, and
you can easily create your own status graphs and organize them
into custom pages and groups.
@@ -24,7 +24,7 @@
<para>
The default graphs provide graphical information about the MySQL
server's current performance, load, and memory usage. Additional
- pages list all server variables, divided into pages for status
+ pages list all server variables, with tabs for memory health, status
variables and system variables. Note that clicking on the status
pages will open an additional connection to the MySQL server,
which you can see when viewing threads and users in the
@@ -34,7 +34,7 @@
<para>
We'll begin by covering the different pre-made status graphs,
- and then describe how to create your own status graphs yourself.
+ and then describe how to create your own status graphs.
Finally we'll describe the pages in the
<literal>Health</literal> section dedicated to the various
status and system variables.
@@ -114,8 +114,8 @@
<para>
This tab provides information about memory caches that affect
the performance of the MySQL server. For each cache, there is a
- display that shows the current hitrate or usage of the cache,
- and a display that shows the hitrate or usage for the last few
+ display that shows the current hit rate or usage of the cache,
+ and a display that shows the hit rate or usage for the last few
minutes.
</para>
@@ -129,9 +129,9 @@
corresponding result that was sent to the client. If an
identical query is later received, the server will retrieve
the results from the query cache rather than parsing and
- executing the same query again. The hitrate indicates the
+ executing the same query again. The hit rate indicates the
ratio of queries that were cached and queries that were not
- cached. The higher the hitrate, the better the performance
+ cached. The higher the hit rate, the better the performance
of the server regarding <literal>SELECT</literal> queries.
See the
<ulink url="http://dev.mysql.com/doc/mysql/en/Query_Cache.html">MySQL
@@ -150,8 +150,8 @@
Variables</link> section. The line graph is an indication of
the number of <literal>key_read_requests</literal> that
resulted in actual <literal>key_reads</literal>. The higher
- the hitrate the more effective your key buffer is. A low
- hitrate can indicate that you need to increate the size of
+ the hit rate the more effective your key buffer is. A low
+ hit rate can indicate that you need to increase the size of
your keycache.
</para>
</listitem>
@@ -167,7 +167,7 @@
<title>Creating Custom Health Graphs</title>
<para>
- While the pre-made status graphs can provide you with informatin
+ While the pre-made status graphs can provide you with information
of the current state of your MySQL server, there may be
additionally information that you wish to visually track. The
&administrator; <literal>Health</literal> section allows you to
@@ -188,9 +188,9 @@
<para>
Once you have created a new page, you will need to create a
- group. All graphs are located within groups. For example, the
+ group. All graphs are organized into groups. For example, the
<literal>Key buffer usage</literal> and <literal>Key buffer
- hitrate</literal> graphs are both located within a group titled
+ hit rate</literal> graphs are both members of the group titled
<literal>Key Efficiency</literal>. To create a group,
right-click within your newly created page and choose the
<guimenu>Add a Group</guimenu> option.
@@ -249,7 +249,7 @@
<para>
If we wanted to track the number of temporary tables created on
- a continious basis, we could use the following as our formula:
+ a continuous basis, we could use the following as our formula:
</para>
<programlisting>
@@ -261,7 +261,7 @@
Unit</literal> that best represents your data. You can choose
from <literal>Percentage</literal>, <literal>Count</literal>,
<literal>Byte</literal>, and <literal>Seconds</literal>. In our
- examples we would have used <literal>Percentage</literal> for
+ examples we would use <literal>Percentage</literal> for
the first example, and <literal>Count</literal> for the second.
You can also assign a caption to the value.
</para>
@@ -280,7 +280,7 @@
<para>
You can also set the <literal>Max. Value</literal> option by way
- of a formula assigned in the <guilabel>Max Formular</guilabel>
+ of a formula assigned in the <guilabel>Max Formula</guilabel>
field. The same syntax applies in this field as applies in the
<guilabel>Value Formula</guilabel> field. For example, if you
were creating a bar graph tracking the number of temporary disk
@@ -288,7 +288,7 @@
<literal>[created_tmp_disk_tables]</literal> as the
<guilabel>Value Formula</guilabel> and
<literal>[created_tmp_tables]</literal> as the <guilabel>Max.
- Formular</guilabel>.
+ Formula</guilabel>.
</para>
<remark>
@@ -348,7 +348,7 @@
<para>
For each category, and each subcategory, the system variables
are listed in the right box of the working area, together with
- their values, and with a short explanation. The system variables
+ their values and a short explanation. The system variables
are described in detail in the
<ulink url="http://dev.mysql.com/doc/mysql/en/SHOW_VARIABLES.html"><literal>SHOW
VARIABLES</literal></ulink> section of the reference manual.
@@ -358,10 +358,10 @@
System variables that can be set at runtime are marked as
editable, that is they are prefixed with an icon different from
the variables that cannot be set at runtime. Double-clicking on
- editable variables will open a dialog where you can specify
+ editable variables will open a dialog box allowing you to specify
another value for the variable. The changes you make will take
- effect as soon as you click the <guibutton>OK</guibutton> button
- in that dialog. Click <guibutton>Abort</guibutton> if you want
+ effect as soon as you confirm the changes by clicking the <guibutton>OK</guibutton> button.
+ Click <guibutton>Abort</guibutton> if you want
to keep the current value. Changes made in this manner will only
persist until the server is restarted, after which the server
will revert to it's startup settings. In &administrator;, system
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3146 - trunk/administrator | plavin | 30 Aug |
