The branch, master has been updated via b0ed51d8cdaa0ec42649f6258932889687890594 (commit) from 4adf3478e6b64d7ea77e8d5cdffa4f7cd829f56d (commit)

- Log ----------------------------------------------------------------- commit b0ed51d8cdaa0ec42649f6258932889687890594 Author: Piotr Przybylski piotrprz@gmail.com Date: Sat Aug 20 13:51:06 2011 +0200

Remove todo item

-----------------------------------------------------------------------

Summary of changes: libraries/advisory_rules.txt | 1 - 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/libraries/advisory_rules.txt b/libraries/advisory_rules.txt index c3445e0..7745157 100644 --- a/libraries/advisory_rules.txt +++ b/libraries/advisory_rules.txt @@ -214,7 +214,6 @@ rule 'Rate of reading first index entry' 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)

-# This rule may be applicable to MyISAM-only workloads, but completely wrong for InnoDB - http://www.mysqlperformanceblog.com/2010/06/15/what-does-handler_read_rnd-me... rule 'Rate of reading fixed position' Handler_read_rnd / Uptime value * 60 * 60 > 1

hooks/post-receive