number of rows deleted from InnoDB tables.Innodb_rows_insertedThe number of rows inserted in InnoDB tables.Innodb_rows_readThe number of rows read from InnoDB tables.Innodb_rows_updatedThe number of rows updated in InnoDB tables. Thread CacheNumber of threads that can be cachedThread_cache_sizeNumber of threads in the cacheThreads_cachedThreads created to handle connectionsThreads_createdThread cache hit rate(Threads_created/ Threads_connected) * 100Table CacheNo. of tables that can be cachedTable_cacheThe number of open tables for all threads. Increasing this value increases the number of file descriptors that mysqld requires.Tables currently openOpen-tablesNo. of table cache missesOpened_tablesIf the number increases rapidly, consider increasing the table_cache.Query CacheQuery cache enabledHave_query_cacheQuery Cache TypeQuery_cache_typeOff: query has been disabled; Always: all statements are cached except those beginning with SELECT SQL_NO_CACHE; Demand: Caching is done only for those beginning with SELECT SQL_CACHE.Cache SizeQuery_cache_sizeMax size of cached queryQuery_cache_limitThe maximum size of individual query results that can be cached.Free MemoryQcache_free_memoryThe amount of free memory in the query cache.Query parsing and execution bufferQuery_prealloc_sizeBetter performance by increasing this value, if you execute a lot of complex queries.Block SizeQuery_cache_min_res_unitFor queries with large resultset, larger block size means better performance; but for queries with small resultset, a large block size leads to memory fragmentation.Total BlocksQcache_total_blocksTotal number of blocks in the cacheFree BlocksQcache_free_blocksTotal number of free blocks in the cacheFragmentationQcache_free_blocks *100/ Qcache_total_blocksExtent of fragmentation in the query cache.Queries in cacheQcache_queries_in_cacheQueries not cachedQcache_not_cachedQueries that cannot be cached, since it contains UDFs, user variables or it accesses system database.Queries inserted to cacheQcache_insertsCache HitsQcache_hitsNumber of queries that served successfully by the query cache.Queries pruned from cacheQcache_lowmem_prunesQueries that were inserted into the query cache, but subsequently got pruned, because of low memory.Pruned as percentage of insertsQcache_lowmem_prunes* 100/ Qcache_insertsIf this rate is high, consider increasing Query_cache_size system variable.Cache Hit RateQcache_hits * 100 / (Qcache_hits + Qcache_inserts)A high rate indicates that queries in cache are being reused by other threads; a low rate shows either not enough memory allocated to query cache or identical queries are not repeatedly issued to the server.Sort BuffersBuffer for in-memory sortingSort_buffer_sizeIt is allocated per client, so dont make it too large; recommended 1 M.Temporary files created because of insufficient Sort_buffer_sizeSort_merge_passesIf this value is high, increase the value of Sort_buffer_size.Buffer for fast rebuilds of MyISAM indexesMyisam_sort_buffer_sizeIt is allocated per client.Buffer for reading rows in sorted order after a sort operationRead_rnd_buffer_sizeIt is allocated per client.Table LocksAcquired immediatelyTable_locks_immediateNumber of times table locks are acquired immediately.Wait was neededTable_locks_waitedNumber of times a wait was required before getting a table lock. If this is high, and you have performance problems, you should first optimize your queries, and then either split your table or tables.Lock contentionTable_locks_waited * 100 / (Table_locks_waited + Table_locks_immediate)Full Table ScansNumber of requests to read a row based on a fixed positionhandler_read_rndThis value is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan entire tables or you have joins that dont use keys properly.Number of requests to read the next row in the data file.handler_read_rnd_nextThis value is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly