Some improvements to Query Cache text (by Colin Faber).

parent 73628811
...@@ -34298,14 +34298,15 @@ Following are some performance data for the query cache ...@@ -34298,14 +34298,15 @@ Following are some performance data for the query cache
@itemize @bullet @itemize @bullet
@item @item
If you don't use the query cache (@code{query_cache_size=0}), there is If want to disable the query cache code set @code{query_cache_size=0}.
no notable overhead. By disabling the query cache code there is no noticeable overhead.
@item @item
If all queries are very simple (like selecting a row from a table with If all of the queries you're preforming are simple (such as selecting a
one row) but still different so that the queries can't be cached, the row from a table with one row); but still differ so that the queries can
overhead for having the query cache active is 13%. This could be not be cached, the overhead for having the query cache active is 13%.
regarded as the worst case scenario. In real life queries are much more This could be regarded as the worst case scenario. However, in real life,
complicated than this so the overhead is normally significantly lower. queries are much more complicated than our simple example so the overhead
is normally significantly lower.
@item @item
Searches after one row in a one row table is 238% faster. 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 This can be regarded as close to the minimum speedup to be expected for
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment