DB Tuning

Thread Cache Monitor
Threads CreatedConnectionsThread Cache SizeHit RatioWarnings
12638395440%The ideal situation is to get Threads Created as close as possible to Thread Cache Size. So no new connections are having to wait for new thread allocation. Stay as close to a 99% hit ratio as you can as this will reduce bottlenecks in your caching. Adjust your Thread Cache Size until this is achieved. You can set your Thread Cache Size on the fly by doing "SET GLOBAL thread_cache_size=N". Where N is the desired size of your Thread Cache. For additional information on the SET command please read SET Syntax

Table Cache Monitor
Table CacheOpen TablesOpened TablesWarnings
204820480Your MySQL server has not been running long enough to make a quality assessment of the performance of your table cache. Put some traffic on there and come back soon!Uptime: 2491375

Query Cache Monitor
Query Cache Ratio0.09
Query Cache Inserts7205575
Query Cache Hits82317490
Query Cache Available?YES
Query Cache Size20971520
Query Cache TypeON
Query Cache Free Memory8974840
Query Cache Free Blocks2751If your Query Cache has a lot of free blocks in it. This can indicate fragmentation in your Query Cache. This can decrease performance and generally just be a waste of resoures. Fix this problem by issuing a 'FLUSH QUERY CACHE' command. Read more about query cache maintenance here.
Query Cache Prunes4479639
Query Cache Limit1048576
Queries Not Cached1719928

Memory Monitor
Minimum Memory Needed : 1933492216
This number is a calculation of the maximum amount of memory your mySQL instance will consume on your server . It is a sum of all the caches and buffers that would benefit by not using swap or not having to goto the HD. Having a number larger than your total available amount of memory will result in swapping.
Min_memory_needed = key_buffer + innodb_buffer_pool + innodb_log_buffer + innodb_additional_mem_pool + net_buffer + max_connections * (read_buffer + join_buffer + sort_buffer + myisam_sort_buffer + thread_stack + tmp_table_size + read_rnd_buffer)
Key Buffer : 8384512
InnoDB Buffer Pool : 8388608
InnoDB Log Buffer : 1048576
InnoDB Additional Memory Pool : 1048576
Net Buffer : 16384
Max Connections : 100
Read Buffer : 131072
Join Buffer : 131072
Sort Buffer : 2097144
Myisam Sort Buffer : 8388608
Thread Stack : 262144
Tmp Table Size : 33554432
Read Rnd Buffer Size : 262144

Select Monitor
Variable NameCurrent ValueWarnings
Select_full_join0A high value here means that MySQL is not using indexes and is therefore taking longer to build a result set. The problem can be fixed by indexing important fields of the join.Enable the Slow Query Log and use Explain to examine your queries.
Select_scan33A high value here can be an indication of bottlenecks in your server optimization. This happens because Mysql is not using the indexes for the tables and so is having to do extra work for inefficient queries. Enable the Slow Query Log and use Explain to examine your queries.

Syndicate

Syndicate content