Invalidating query cache entries mysql

My SQL Caching To make queries faster to respond is to use caching, a cache stores frequently used data in a place that is local where is can be accessed faster.Cached data can be stored either on a computers local hard disk or in the computers internal memory.Hello, I've got this question about query cache in mysql 4 - when I do query like this: SELECT SQL_CACHE column_a FROM table_a WHERE column_a = 'const';and then I update table like this: UPDATE table_a SET column_b = column_b 1; cache entry is invalidated and deleted (I hope, I understood mysql sources correctly - I made just a quick look into query_cache.cc).Mechanism for cleaning cache entries deletes them always, when any table from cached query is modified.My SQL is no different in that the larger the cache the more data that can be stored and hopefully when a user runs a SQL query the information will be cached in memory and not on the local hard drive, the way to think of accessing data when using a database is the following Thus you want to get that data that the users needs into memory which will greatly give a better performance and experience to your end user, now as databases can be very large it some times impossible to get all the data into cache, however if you can get the most used data into cache then the users experience will be greatly improved, you don't want your user hanging around waiting for information otherwise he/she may go somewhere else which could be a disaster for your business.My SQL implements caching where frequently used data can be stored, there are two parts to a query can use the query cache to obtain the already prepared query without running this process again which costs time, hopefully the data retrieved will be pretty much the same, again this data should still be in the data cache (memory) which means for faster retrieval.

So if it's storing those query results then it's completely worthless because chances are no one is going to run that same exact query again.I know that this needs some more memory for the query cache, and need some additional query parsing.Since I'm a beginner in this area I would like to know whether this is doable and any problems that may arise ....In fact, with RBR there is a binlog event for each modified row, thus the mutex is acquired for every row. Hi, I'm thinking of extending the query cache to deal with following scenarios, 1.Still this is in idea level and I haven't done any coding yet.

You must have an account to comment. Please register or login here!