MySQL的SHOW STATUS

SQL 查询变量值描述Flush_commands1The number of executed FLUSH statements.Last_query_cost0The total cost of the last compiled query as computed by the query optimizer. Useful for comparing the cost of different query plans for the same query. The default value of 0 means that no query has been compiled yet.Slow_queries0The number of queries that have taken more than long_query_time seconds.开始 InnoDB变量值描述变量 InnoDB 状态 Innodb_buffer_pool_pages_data19The number of pages containing data (dirty or clean).Innodb_buffer_pool_pages_dirty0The number of pages currently dirty.Innodb_buffer_pool_pages_flushed1The number of buffer pool pages that have been requested to be flushed.Innodb_buffer_pool_pages_free493The number of free pages.Innodb_buffer_pool_pages_misc0The number of pages busy because they have been allocated for administrative overhead such as row locks or the adaptive hash index. This value can also be calculated as Innodb_buffer_pool_pages_total - Innodb_buffer_pool_pages_free - Innodb_buffer_pool_pages_data.Innodb_buffer_pool_pages_total512Total size of buffer pool, in pages.Innodb_buffer_pool_read_ahead_rnd1The number of "random" read-aheads InnoDB initiated. This happens when a query is to scan a large portion of a table but in random order.Innodb_buffer_pool_read_ahead_seq0The number of sequential read-aheads InnoDB initiated. This happens when InnoDB does a sequential full table scan.Innodb_buffer_pool_read_requests84The number of logical read requests InnoDB has done.Innodb_buffer_pool_reads12The number of logical reads that InnoDB could not satisfy from buffer pool and had to do a single-page read.Innodb_buffer_pool_wait_free0Normally, writes to the InnoDB buffer pool happen in the background. However, if it's necessary to read or create a page and no clean pages are available, it's necessary to wait for pages to be flushed first. This counter counts instances of these waits. If the buffer pool size was set properly, this value should be small.Innodb_buffer_pool_write_requests1The number writes done to the InnoDB buffer pool.Innodb_data_fsyncs7The number of fsync() operations so far.Innodb_data_pending_fsyncs0The current number of pending fsync() operations.Innodb_data_pending_reads0The current number of pending reads.Innodb_data_pending_writes0The current number of pending writes.Innodb_data_read2,494 kThe amount of data read so far, in bytes.Innodb_data_reads25The total number of data reads.Innodb_data_writes7The total number of data writes.Innodb_data_written35 kThe amount of data written so far, in bytes.Innodb_dblwr_pages_written1The number of doublewrite writes that have been performed and the number of pages that have been written for this purpose.Innodb_dblwr_writes1The number of doublewrite writes that have been performed and the number of pages that have been written for this purpose.Innodb_log_waits0The number of waits we had because log buffer was too small and we had to wait for it to be flushed before continuing.Innodb_log_write_requests0The number of log write requests.Innodb_log_writes2The number of physical writes to the log file.Innodb_os_log_fsyncs5The number of fsyncs writes done to the log file.Innodb_os_log_pending_fsyncs0The number of pending log file fsyncs.Innodb_os_log_pending_writes0Pending log file writes.Innodb_os_log_written1,024The number of bytes written to the log file.Innodb_page_size16 kThe compiled-in InnoDB page size (default 16KB). Many values are counted in pages; the page size allows them to be easily converted to bytes.Innodb_pages_created0The number of pages created.Innodb_pages_read19The number of pages read.Innodb_pages_written1The number of pages written.Innodb_row_lock_current_waits0The number of row locks currently being waited for.Innodb_row_lock_time0The total time spent in acquiring row locks, in milliseconds.Innodb_row_lock_time_avg0The average time to acquire a row lock, in milliseconds.Innodb_row_lock_time_max0The maximum time to acquire a row lock, in milliseconds.Innodb_row_lock_waits0The number of times a row lock had to be waited for.Innodb_rows_deleted0The number of rows deleted from InnoDB tables.Innodb_rows_inserted0The number of rows inserted in InnoDB tables.Innodb_rows_read0The number of rows read from InnoDB tables.Innodb_rows_updated0The number of rows updated in InnoDB tables.开始 SSL变量值描述Ssl_accept_renegotiates0 Ssl_accepts0 Ssl_callback_cache_hits0 Ssl_cipher  Ssl_cipher_list  Ssl_client_connects0 Ssl_connect_renegotiates0 Ssl_ctx_verify_depth0 Ssl_ctx_verify_mode0 Ssl_default_timeout0 Ssl_finished_accepts0 Ssl_finished_connects0 Ssl_session_cache_hits0 Ssl_session_cache_misses0 Ssl_session_cache_modeNONE Ssl_session_cache_overflows0 Ssl_session_cache_size0 Ssl_session_cache_timeouts0 Ssl_sessions_reused0 Ssl_used_session_cache_entries0 Ssl_verify_depth0 Ssl_verify_mode0 Ssl_version  开始 Handler变量值描述Handler_commit0The number of internal COMMIT statements.Handler_delete14 kThe number of times a row was deleted from a table.Handler_discover0The MySQL server can ask the NDB Cluster storage engine if it knows about a table with a given name. This is called discovery. Handler_discover indicates the number of time tables have been discovered.Handler_prepare0 Handler_read_first13 kThe number of times the first entry was read from an index. If this is high, it suggests that the server is doing a lot of full index scans; for example, SELECT col1 FROM foo, assuming that col1 is indexed.Handler_read_key402 kThe number of requests to read a row based on a key. If this is high, it is a good indication that your queries and tables are properly indexed.Handler_read_next369 kThe number of requests to read the next row in key order. This is incremented if you are querying an index column with a range constraint or if you are doing an index scan.Handler_read_prev4,226The number of requests to read the previous row in key order. This read method is mainly used to optimize ORDER BY ... DESC.Handler_read_rnd49 kThe number of requests to read a row based on a fixed position. This 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 whole tables or you have joins that don't use keys properly.Handler_read_rnd_next5,277 kThe number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.Handler_rollback0The number of internal ROLLBACK statements.Handler_savepoint0 Handler_savepoint_rollback0 Handler_update11 kThe number of requests to update a row in a table.Handler_write391 kThe number of requests to insert a row in a table.开始 Query cache变量值描述Flush query cache Qcache_free_blocks851The number of free memory blocks in query cache.Qcache_free_memory6,297 kThe amount of free memory for query cache.Qcache_hits513 kThe number of cache hits.Qcache_inserts100 kThe number of queries added to the cache.Qcache_lowmem_prunes8,821The number of queries that have been removed from the cache to free up memory for caching new queries. This information can help you tune the query cache size. The query cache uses a least recently used (LRU) strategy to decide which queries to remove from the cache.Qcache_not_cached14 kThe number of non-cached queries (not cachable, or not cached due to the query_cache_type setting).Qcache_queries_in_cache4,049The number of queries registered in the cache.Qcache_total_blocks9,528The total number of blocks in the query cache.开始 Threads变量值描述显示进程 Slow_launch_threads0The number of threads that have taken more than slow_launch_time seconds to create.Threads_cached3The number of threads in the thread cache. The cache hit rate can be calculated as Threads_created/Connections. If this value is red you should raise your thread_cache_size.Threads_connected5The number of currently open connections.Threads_created8The number of threads created to handle connections. If Threads_created is big, you may want to increase the thread_cache_size value. (Normally this doesn't give a notable performance improvement if you have a good thread implementation.)Threads_running2The number of threads that are not sleeping.Threads_cache_hitrate_%99.98 % 开始 二进制日志变量值描述Binlog_cache_disk_use0The number of transactions that used the temporary binary log cache but that exceeded the value of binlog_cache_size and used a temporary file to store statements from the transaction.Binlog_cache_use0The number of transactions that used the temporary binary log cache.开始 Temporary data变量值描述Created_tmp_disk_tables2,004The number of temporary tables on disk created automatically by the server while executing statements. If Created_tmp_disk_tables is big, you may want to increase the tmp_table_size value to cause temporary tables to be memory-based instead of disk-based.Created_tmp_files5How many temporary files mysqld has created.Created_tmp_tables19 kThe number of in-memory temporary tables created automatically by the server while executing statements.开始 Delayed inserts变量值描述Delayed_errors0The number of rows written with INSERT DELAYED for which some error occurred (probably duplicate key).Delayed_insert_threads0The number of INSERT DELAYED handler threads in use. Every different table on which one uses INSERT DELAYED gets its own thread.Delayed_writes0The number of INSERT DELAYED rows written.Not_flushed_delayed_rows0The number of rows waiting to be written in INSERT DELAYED queues.开始 Key cache变量值描述Key_blocks_not_flushed0The number of key blocks in the key cache that have changed but haven't yet been flushed to disk. It used to be known as Not_flushed_key_blocks.Key_blocks_unused13 kThe number of unused blocks in the key cache. You can use this value to determine how much of the key cache is in use.Key_blocks_used919The number of used blocks in the key cache. This value is a high-water mark that indicates the maximum number of blocks that have ever been in use at one time.Key_read_requests3,678 kThe number of requests to read a key block from the cache.Key_reads16 kThe number of physical reads of a key block from disk. If Key_reads is big, then your key_buffer_size value is probably too small. The cache miss rate can be calculated as Key_reads/Key_read_requests.Key_write_requests719 kThe number of requests to write a key block to the cache.Key_writes644 kThe number of physical writes of a key block to disk.Key_buffer_fraction_%19.13 % Key_write_ratio_%89.58 % Key_read_ratio_%0.43 % 开始 Joins变量值描述Select_full_join336The number of joins that do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.Select_full_range_join0The number of joins that used a range search on a reference table.Select_range8,445The number of joins that used ranges on the first table. (It's normally not critical even if this is big.)Select_range_check0The number of joins without keys that check for key usage after each row. (If this is not 0, you should carefully check the indexes of your tables.)Select_scan18 kThe number of joins that did a full scan of the first table.开始 Replication变量值描述Show slave hosts Show slave status Rpl_statusNULLThe status of failsafe replication (not yet implemented).Slave_open_temp_tables0The number of temporary tables currently open by the slave SQL thread.Slave_retried_transactions0Total (since startup) number of times the replication slave SQL thread has retried transactions.Slave_runningOFFThis is ON if this server is a slave that is connected to a master.开始 Sorting变量值描述Sort_merge_passes0The number of merge passes the sort algorithm has had to do. If this value is large, you should consider increasing the value of the sort_buffer_size system variable.Sort_range2,913The number of sorts that were done with ranges.Sort_rows52 kThe number of sorted rows.Sort_scan2,563The number of sorts that were done by scanning the table.开始 个表变量值描述Flush (close) all tables Show open tablesOpen_tables64The number of tables that are open.Opened_tables38 kThe number of tables that have been opened. If opened tables is big, your table cache value is probably too small.Table_locks_immediate326 kThe number of times that a table lock was acquired immediately.Table_locks_waited43The number of times that a table lock could not be acquired immediately and a wait was needed. If this is high, and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.开始 Transaction coordinator变量值描述Tc_log_max_pages_used0 Tc_log_page_size0 Tc_log_page_waits0 
开始 变量值描述CompressionOFF Open_files127The number of files that are open.Open_streams0The number of streams that are open (used mainly for logging).Open_table_definitions256 Opened_files237 k Opened_table_definitions33 k Prepared_stmt_count0 Queries994 k Uptime_since_flush_status3,627 k