Invalidating query cache entries replication
04-Apr-2020 07:00
This has the implication that the query cache cannot be enabled at runtime. After review, it may be pushed to the relevant source trees for release in the next version.
You can access the patch from: 2900 Kristofer Pettersson 2009-10-29 Bug#38551 query cache can still consume [very little] cpu time even when it is off.
After review, it may be pushed to the relevant source trees for release in the next version.
You can access the patch from: 2735 Kristofer Pettersson 2008-09-08 Bug#38551 query cache can still consume [very little] cpu time even when it is off.
Currently nobody wants: 1) a blocking mutex 2) a client barrier on a write.
3) Only be able to disable query cache at compile time/startup time.
You can access the patch from: 2768 Kristofer Pettersson 2008-10-09 Bug#38551 query cache can still consume [very little] cpu time even when it is off.
By checking query_cache_size before attempting to invalidate a table or db we avoid grabbing the query cache mutex.
By using the command line option --query_cache_type=0, the user can disable the query cache permanently and avoid taking the query cache mutex. After review, it may be pushed to the relevant source trees for release in the next version.
However, the Query Cache still does some work before finding out that query_cache_size is 0 and returning.