Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
"Transparent caching" is in mysql itself.
It works so well and transparently that you don't even know about it.
The problem arises when you need to invalidate the cache. For example, updating some records. Therefore, the transparent caching you invented will have to repeat the behavior of the mysql cache - delete all queries containing the updated table. So why write what has already been written?
Hence the conclusion: if you want to speed up something even faster than the mysql cache, caching should not be transparent. Each operator must at least indicate the estimated lifetime of the result in the cache.
However, try to pick up this script for mysql-proxy: github.com/clofresh/mysql-proxy-cache
of
course it caches everything ignoring the application logic.
I don't understand why such a solution might be needed.
Built-in query caching can be controlled explicitly via the SQL_CACHE and SQL_NO_CACHE keywords.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question