The branch, master has been updated
via 05e3e69e83be71bd7571abe52e8e02801eef43c6 (commit)
from 9ac55da51cd11186785ca3bb07e43067f03f2404 (commit)
- Log -----------------------------------------------------------------
commit 05e3e69e83be71bd7571abe52e8e02801eef43c6
Author: Michal Čihař <[email protected]>
Date: Thu Aug 11 15:10:29 2011 +0200
Fix more typos
-----------------------------------------------------------------------
Summary of changes:
libraries/advisory_rules.txt | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/libraries/advisory_rules.txt b/libraries/advisory_rules.txt
index c43d838..96b0385 100644
--- a/libraries/advisory_rules.txt
+++ b/libraries/advisory_rules.txt
@@ -211,7 +211,7 @@ rule 'rate of reading first index entry'
Handler_read_first / Uptime
value * 60 * 60 > 1
The rate of reading the first index entry is high.
- This usually indicates frequent full index scans. Full index scans are
faster than table scans but require lots of cpu cycles in big tables, if those
tables that have or had high volumes of UPDATEs and DELETEs, running 'OPTIMIZE
TABLE' might reduce the amount of and/or speed up full index scans. Other than
that full index scans can only be reduced by rewriting queries.
+ This usually indicates frequent full index scans. Full index scans are
faster than table scans but require lots of CPU cycles in big tables, if those
tables that have or had high volumes of UPDATEs and DELETEs, running 'OPTIMIZE
TABLE' might reduce the amount of and/or speed up full index scans. Other than
that full index scans can only be reduced by rewriting queries.
Index scans average: %s, this value should be less than 1 per hour |
PMA_bytime(value,2)
rule 'rate of reading fixed position'
@@ -233,14 +233,14 @@ rule 'tmp_table_size vs. max_heap_table_size'
tmp_table_size - max_heap_table_size
value !=0
tmp_table_size and max_heap_table_size are not the same.
- If you have deliberatly changed one of either: The server uses the
lower value of either to determine the maximum size of in-memory tables. So if
you wish to increse the in-memory table limit you will have to increase the
other value as well.
+ If you have deliberately changed one of either: The server uses the
lower value of either to determine the maximum size of in-memory tables. So if
you wish to increase the in-memory table limit you will have to increase the
other value as well.
Current values are tmp_table_size: %s, max_heap_table_size: %s |
implode(' ',PMA_formatByteDown(tmp_table_size, 2, 2)), implode('
',PMA_formatByteDown(max_heap_table_size, 2, 2))
rule '% temp disk tables' [Created_tmp_tables + Created_tmp_disk_tables > 0]
Created_tmp_disk_tables / (Created_tmp_tables +
Created_tmp_disk_tables) * 100
value > 25
Many temporary tables are being written to disk instead of being kept
in memory.
- Increasing {max_heap_table_size} and {tmp_table_size} might help.
However some temporary tables are always being written to disk, independent of
the value of these variables. To elminiate these you will have to rewrite your
queries to avoid those conditions (Within a temprorary table: Presence of a
BLOB or TEXT column or presence of a column bigger than 512 bytes) as mentioned
in the beginning of an <a
href="http://www.facebook.com/note.php?note_id=10150111255065841&comments";>Article
by the Pythian Group</a>
+ Increasing {max_heap_table_size} and {tmp_table_size} might help.
However some temporary tables are always being written to disk, independent of
the value of these variables. To elminiate these you will have to rewrite your
queries to avoid those conditions (Within a temporary table: Presence of a BLOB
or TEXT column or presence of a column bigger than 512 bytes) as mentioned in
the beginning of an <a
href="http://www.facebook.com/note.php?note_id=10150111255065841&comments";>Article
by the Pythian Group</a>
%s% of all temporary tables are being written to disk, this value
should be below 25% | round(value,1)
rule 'temp disk rate'
@@ -362,7 +362,7 @@ rule 'Slow launch time'
rule '% connections used'
Max_used_connections / max_connections * 100
value > 80
- The maximum amount of used connnections is getting close to the value
of max_connections.
+ The maximum amount of used connections is getting close to the value of
max_connections.
Increase max_connections, or decrease wait_timeout so that connections
that do not close database handlers properly get killed sooner. Make sure the
code closes database handlers properly.
Max_used_connections is at %s% of max_connections, it should be below
80% | round(value,1)
@@ -407,7 +407,7 @@ rule '% InnoDB log size' [innodb_buffer_pool_size > 0]
innodb_log_file_size / innodb_buffer_pool_size * 100
value < 20
The InnoDB log file size is not an appropriate size, in relation to the
InnoDB buffer pool.
- Especiallay one a system with a lot of writes to InnoDB tables you
shoud set innodb_log_file_size to 25% of {innodb_buffer_pool_size}. However the
bigger this value, the longer the recovery time will be when database crashes,
so this value should not be set much higher than 256 MiB. Please note however
that you cannot simply change the value of this variable. You need to shutdown
the server, remove the InnoDB log files, set the new value in my.cnf, start the
server, then check the error logs if everything went fine. See also <a
href="http://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html";>this
blog entry</a>
+ Especially one a system with a lot of writes to InnoDB tables you
should set innodb_log_file_size to 25% of {innodb_buffer_pool_size}. However
the bigger this value, the longer the recovery time will be when database
crashes, so this value should not be set much higher than 256 MiB. Please note
however that you cannot simply change the value of this variable. You need to
shutdown the server, remove the InnoDB log files, set the new value in my.cnf,
start the server, then check the error logs if everything went fine. See also
<a
href="http://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html";>this
blog entry</a>
Your InnoDB log size is at %s% in relation to the InnoDB buffer pool
size, it should not be below 20% | round(value,1)
rule 'Max InnoDB log size' [innodb_buffer_pool_size > 0 &&
innodb_log_file_size / innodb_buffer_pool_size * 100 < 30]
hooks/post-receive
--
phpMyAdmin
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it.
http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Phpmyadmin-git mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/phpmyadmin-git
