Anyone using TONS of Query Cache for a high-traffic site? Our search server is really sweating. I was about to jump through a LOT of software loops to program query caching at the app level, when I realized that MySQL had it built-in already. (We're using newest: 4.0.18)
Seems we've got plenty of Qcache_free_memory (see below) - so I'm wondering... Has anyone set their query_cache_size= setting really high like 1GB of RAM - to see how it helps? Any more articles or info on this besides the docs at http://www.mysql.com/doc/en/Query_Cache.html ? | Key_blocks_used | 29625 | | Key_read_requests | 31993562 | | Key_reads | 28450 | | Key_write_requests | 204631 | | Key_writes | 131756 | | Max_used_connections | 140 | | Not_flushed_key_blocks | 0 | | Not_flushed_delayed_rows | 0 | | Open_tables | 100 | | Open_files | 146 | | Open_streams | 0 | | Opened_tables | 106 | | Questions | 1337108 | | Qcache_queries_in_cache | 11363 | | Qcache_inserts | 530809 | | Qcache_hits | 520845 | | Qcache_lowmem_prunes | 0 | | Qcache_not_cached | 1984 | | Qcache_free_memory | 255088000 | | Qcache_free_blocks | 4773 | | Qcache_total_blocks | 27515 | | Rpl_status | NULL | | Select_full_join | 1005 | | Select_full_range_join | 0 | | Select_range | 22 | | Select_range_check | 803 | | Select_scan | 6271 | | Slave_open_temp_tables | 0 | | Slave_running | ON | | Slow_launch_threads | 0 | | Slow_queries | 138 | | Sort_merge_passes | 0 | | Sort_range | 105822 | | Sort_rows | 1479015 | | Sort_scan | 5009 | | Table_locks_immediate | 638173 | | Table_locks_waited | 5449 | | Threads_cached | 8 | | Threads_created | 4300 | | Threads_connected | 111 | | Threads_running | 2 | -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
