indexed or that your queries are not written to take advantage of the indexes you have.Number of times the first entry was read from an indexhandler_read_firstIf this value is high, it suggests that the server is doing a lot of full index scans.Number of requests to read the next row in key order.handler_read_nextThis value is incremented if you are querying an index column with a range constraint or if you are doing an index scan.Number of requests to read a row based on a key.handler_read_keyIf this value is high, it is a good indication that your tables are properly indexed for your queries.Number of requests to read the previous row in key order.handler_read_prevThis read method is mainly used to optimize ORDER BY ... DESC.Percentage of full table scans1-(handler_read_rnd_next + handler_read_rnd) / (handler_read_rnd_next + handler_read_rnd + handler_read_first + handler_read_next + handler_read_key + handler_read_prev )Ratio of the number of rows read via full table scans to the sum of all handler variables (which denotes all row accesses). A high value indicates excessive table scans. You should examine tables and queries for proper use of indexes. Turn on the slow query log, identify the queries using full table scan and tune it.Buffer for full table scans of MyISAM tablesRead_buffer_sizeThis value is per client.SELECTs requiring full table scanSelect_scanA high value indicates that the queries are not tuned to use indexes.Buffer for JOINs requiring full table scanJoin_buffer_sizeThis value is per client.Joins requiring full scan of second and subsequent tablesSelect_full_joinIf the value is high, optimize the queries to use indexes.Temporary TablesMaximum table sizeTmp_table_sizeThe maximum size of an internal table that can be created in memory. If an internal table is larger than this size, it is converted into a MyISAM table on disk.Maximum size of a memory tableMax_heap_table_sizeMySQL uses the lowest value of tmp_table_size and max_heap_table_size.Total tables createdCreated_tmp_tablesNumber of temporary tables created in memory.Temporary tables created on diskCreated_tmp_disk_tablesIf this value is high, try increasing the values of Tmp_table_size and Max_heap_table_size.Slow Launch ThreadsMinimum launch time for a thread to be considered slowSlow_launch_timeNumber of slow launch threadsSlow_launch_threadsGeneral system overload; may be caused by non-optimal queries.Network TrafficBytes Received from all clientsBytes_receivedBytes Sent to all clientsByets_sentBinary LogBinary log enabled?Log_binSynchronized to disk at each write?Sync_binlogSynchronizing is the safest choice since in the event of a crash you lose at most the last transaction.Binary log cache sizeBinlog_cache_sizeIt stores all SQL statements for the binary log during a transaction; used only with transactional engines.Transactions that used cacheBinlog_cache_useTransactions that used the binary log cache.Transactions that got saved in temporary fileBinlog_cache_disk_useNumber of transactions that used a temporary file because of insufficient Binlog_cache_size.Percentage of transactions that got saved in temporary fileBinlog_cache_disk_use * 100 / Binlog_cache_useSlow Query LogEnabled?Log_slow_queriesIdentifies queries running slow.Min. execution time for a query to be considered slowLong_query_timeNo. of slow queriesSlow_queriesNumber of queries that took more than long_query_time to execute.StatementsAll StatementsQuestionsTotal number of statements sent to the server by all clients.SELECTsCom_select + Qcache_hitsINSERTsCom_insert + Com_replaceUPDATEsCom_updateDELETEsCom_deletePercentage of total Data Manipulation StatementsSystemCPU UsageTotal MemoryMemory Used by MySQLMemory FreeMemory Requirement by MySQL if max users are connectedInnodb_buffer_pool_size + Key_buffer_size + Max_connections * (sort_buffer_size + read_buffer_size + binlog_cache_size) + max_connections *