Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have read the query_cache as a very important tool to improve query performance.
A general recommendation would be to have it enabled to on-demand (using SELECT SQL_CACHE, with a query_cache_type = 2 config setting).
The usefullness of the query-cache is mainly dependent on 4 things:
A simple example: say you have a big table with 10 billion rows and you query a difficult “count” operation on it. It will last very long, give you a tiny result-set. Now if you repeatedly execute that query without changing the table too often, the benefit of query-caching is simply huge.
I hope the principles are somewhat clearer now.