diff options
author | unknown <arjen@co3064164-a.bitbike.com> | 2001-12-12 18:04:40 +1000 |
---|---|---|
committer | unknown <arjen@co3064164-a.bitbike.com> | 2001-12-12 18:04:40 +1000 |
commit | 927b452823a7e3323094aae7fc76dd5ac27965b2 (patch) | |
tree | 50c00fa03e216899e94834e141bbd3e321c7874d /Docs | |
parent | 933d747cec3de4d80c2d72ba1ca64a3245e69675 (diff) | |
download | mariadb-git-927b452823a7e3323094aae7fc76dd5ac27965b2.tar.gz |
Some improvements to Query Cache text (by Colin Faber).
Diffstat (limited to 'Docs')
-rw-r--r-- | Docs/manual.texi | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/Docs/manual.texi b/Docs/manual.texi index 853874ae874..de71b9a6f4f 100644 --- a/Docs/manual.texi +++ b/Docs/manual.texi @@ -34298,14 +34298,15 @@ Following are some performance data for the query cache @itemize @bullet @item -If you don't use the query cache (@code{query_cache_size=0}), there is -no notable overhead. -@item -If all queries are very simple (like selecting a row from a table with -one row) but still different so that the queries can't be cached, the -overhead for having the query cache active is 13%. This could be -regarded as the worst case scenario. In real life queries are much more -complicated than this so the overhead is normally significantly lower. +If want to disable the query cache code set @code{query_cache_size=0}. +By disabling the query cache code there is no noticeable overhead. +@item +If all of the queries you're preforming are simple (such as selecting a +row from a table with one row); but still differ so that the queries can +not be cached, the overhead for having the query cache active is 13%. +This could be regarded as the worst case scenario. However, in real life, +queries are much more complicated than our simple example so the overhead +is normally significantly lower. @item Searches after one row in a one row table is 238% faster. This can be regarded as close to the minimum speedup to be expected for |