MySQL培训3(培训教程).ppt

* RHEL Clustering Storage Management page:* 恢复 10SQL: 8 WRITE InnoDB 数据文件 TID old_value new_value * RHEL Clustering Storage Management page:* Any SELECT query that MySQL doesn’t serve from the cache is a cache miss A cache miss can occur for any of the following reasons: The query is not cacheable, either because it contains a nondeterministic construct (such as CURRENT_DATE) or because its result set is too large to store The server has never seen the query before, so it never had a chance to cache its result The query’s result was previously cached, but the server removed it This can happen because there wasn’t enough memory to keep it because someone instructed the server to remove it or because it was invalidated * RHEL Clustering Storage Management page:* Query cache memory usage and tuning The query cache for the server is stored completely in memory, and does not persist across mysqld restarts Aside from about 40k of memory used by the query cache, the entire pool of memory is initialized as a single contiguous chunk of memory During query cache operation this chunk of memory is divided up into smaller blocks Each block must be at least the size specified by query_cache_min_res_unit, which defaults to 4 Kb In addition to these blocks containing the result sets of the queries there are two hash tables Query hashes The list of database tables that each cached query reference When a table is modified, this second hash table is consultedto determine which queries should be removed due to query cache invalidation * RHEL Clustering Storage Management page:* Seven system variables are used to control the configuration and memory usage of the query cache The values of these can be seen by using SHOW GLOBAL VARIABLES statement or in the GLOBAL_VARIABLES system view in the INFORMATION_SCHEMA * RHEL Clustering Storage Management page:* Query Cache System Variables * RHEL Clustering Storage Management page:* Query cache status variables There are eight status varia