Hi,
playing with my admin about cache size (there was a question today related
to the cache size), noticed a strange thing with cache. It's Windows,
initially it was v3.6.10, but the same is for 3.7.2
I sometimes mentioned that I can track vfs requests for every select in my
admin. In this case
Is it ok for cache to behave like this or some optimization is possible to
fix this?
For this particular case I believe you can do some optimization by
making your own implementation of cache.
Also I believe such strange behavior of cache is pretty much
explainable. Remember that standard
On Wed, Sep 22, 2010 at 7:12 PM, Pavel Ivanov paiva...@gmail.com wrote:
Is it ok for cache to behave like this or some optimization is possible
to
fix this?
For this particular case I believe you can do some optimization by
making your own implementation of cache.
Also I believe such
One real world example is a full table rereading
(rescanning) if a table occasionally has the size from cache_size +1 to
maybe 1.5*cache_size. For default sqlite cache size it's rereading of 2M to
3M tables. Not so great disadvantage to change the algorithm.
Yes, whenever one finds