From 2f48cd69eb74f48565b7505e4dd3cb6ce8844683 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michal=20=C4=8Ciha=C5=99?= Date: Tue, 23 Jul 2013 11:34:33 +0200 Subject: [PATCH] Fix rule definition (value and check were mixed) --- libraries/advisory_rules.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libraries/advisory_rules.txt b/libraries/advisory_rules.txt index 3ffa1d9faf..354791c12b 100644 --- a/libraries/advisory_rules.txt +++ b/libraries/advisory_rules.txt @@ -200,8 +200,8 @@ rule 'Query cache max size' [!fired('Query cache disabled')] Current query cache size: %s | implode(' ',ADVISOR_formatByteDown(value, 2, 2)) rule 'Query cache min result size' [!fired('Query cache disabled')] - value == 1024*1024 query_cache_limit + value == 1024*1024 The max size of the result set in the query cache is the default of 1 MiB. Changing {query_cache_limit} (usually by increasing) may increase efficiency. This variable determines the maximum size a query result may have to be inserted into the query cache. If there are many query results above 1 MiB that are well cacheable (many reads, little writes) then increasing {query_cache_limit} will increase efficiency. Whereas in the case of many query results being above 1 MiB that are not very well cacheable (often invalidated due to table updates) increasing {query_cache_limit} might reduce efficiency. query_cache_limit is set to 1 MiB