5.1.6. Server Status Variables
来源:互联网 发布:centos apache 配置 编辑:程序博客网 时间:2024/06/05 08:16
5.1.6. Server Status Variables
The server maintains many status variables that provide information about its operation. You can view these variables and their values by using the SHOW [GLOBAL | SESSION] STATUS
statement (see Section 13.7.5.32, “SHOW STATUS
Syntax”). The optional GLOBAL
keyword aggregates the values over all connections, and SESSION
shows the values for the current connection.
mysql> SHOW GLOBAL STATUS;
+-----------------------------------+------------+| Variable_name | Value |+-----------------------------------+------------+| Aborted_clients | 0 || Aborted_connects | 0 || Bytes_received | 155372598 || Bytes_sent | 1176560426 |...| Connections | 30023 || Created_tmp_disk_tables | 0 || Created_tmp_files | 3 || Created_tmp_tables | 2 |...| Threads_created | 217 || Threads_running | 88 || Uptime | 1389872 |+-----------------------------------+------------+
Before MySQL 5.0.2, SHOW STATUS
returned global status values. Because the default as of 5.0.2 is to return session values, this is incompatible with previous versions. To issue a SHOW STATUS
statement that will retrieve global status values for all versions of MySQL, write it like this:
SHOW /*!50002 GLOBAL */ STATUS;
Many status variables are reset to 0 by the FLUSH STATUS
statement.
The following table lists all available server status variables:
Table 5.4. Status Variable Summary
Aborted_clients
numericGLOBAL
Aborted_connects
numericGLOBAL
Binlog_cache_disk_use
numericGLOBAL
Binlog_cache_use
numericGLOBAL
Bytes_received
numericGLOBAL
| SESSION
Bytes_sent
numericGLOBAL
| SESSION
Com_admin_commands
numericGLOBAL
| SESSION
Com_alter_db
numericGLOBAL
| SESSION
Com_alter_event
numericGLOBAL
| SESSION
Com_alter_table
numericGLOBAL
| SESSION
Com_analyze
numericGLOBAL
| SESSION
Com_backup_table
numericGLOBAL
| SESSION
Com_begin
numericGLOBAL
| SESSION
Com_call_procedure
numericGLOBAL
| SESSION
Com_change_db
numericGLOBAL
| SESSION
Com_change_master
numericGLOBAL
| SESSION
Com_check
numericGLOBAL
| SESSION
Com_checksum
numericGLOBAL
| SESSION
Com_commit
numericGLOBAL
| SESSION
Com_create_db
numericGLOBAL
| SESSION
Com_create_event
numericGLOBAL
| SESSION
Com_create_function
numericGLOBAL
| SESSION
Com_create_index
numericGLOBAL
| SESSION
Com_create_table
numericGLOBAL
| SESSION
Com_create_user
numericGLOBAL
| SESSION
Com_dealloc_sql
numericGLOBAL
| SESSION
Com_delete
numericGLOBAL
| SESSION
Com_delete_multi
numericGLOBAL
| SESSION
Com_do
numericGLOBAL
| SESSION
Com_drop_db
numericGLOBAL
| SESSION
Com_drop_event
numericGLOBAL
| SESSION
Com_drop_function
numericGLOBAL
| SESSION
Com_drop_index
numericGLOBAL
| SESSION
Com_drop_table
numericGLOBAL
| SESSION
Com_drop_user
numericGLOBAL
| SESSION
Com_execute_sql
numericGLOBAL
| SESSION
Com_flush
numericGLOBAL
| SESSION
Com_grant
numericGLOBAL
| SESSION
Com_ha_close
numericGLOBAL
| SESSION
Com_ha_open
numericGLOBAL
| SESSION
Com_ha_read
numericGLOBAL
| SESSION
Com_help
numericGLOBAL
| SESSION
Com_insert
numericGLOBAL
| SESSION
Com_insert_select
numericGLOBAL
| SESSION
Com_kill
numericGLOBAL
| SESSION
Com_load
numericGLOBAL
| SESSION
Com_lock_tables
numericGLOBAL
| SESSION
Com_optimize
numericGLOBAL
| SESSION
Com_preload_keys
numericGLOBAL
| SESSION
Com_prepare_sql
numericGLOBAL
| SESSION
Com_purge
numericGLOBAL
| SESSION
Com_purge_before_date
numericGLOBAL
| SESSION
Com_rename_table
numericGLOBAL
| SESSION
Com_repair
numericGLOBAL
| SESSION
Com_replace
numericGLOBAL
| SESSION
Com_replace_select
numericGLOBAL
| SESSION
Com_reset
numericGLOBAL
| SESSION
Com_restore_table
numericGLOBAL
| SESSION
Com_revoke
numericGLOBAL
| SESSION
Com_revoke_all
numericGLOBAL
| SESSION
Com_rollback
numericGLOBAL
| SESSION
Com_savepoint
numericGLOBAL
| SESSION
Com_select
numericGLOBAL
| SESSION
Com_set_option
numericGLOBAL
| SESSION
Com_show_binlog_events
numericGLOBAL
| SESSION
Com_show_binlogs
numericGLOBAL
| SESSION
Com_show_charsets
numericGLOBAL
| SESSION
Com_show_collations
numericGLOBAL
| SESSION
Com_show_column_types
numericGLOBAL
| SESSION
Com_show_create_db
numericGLOBAL
| SESSION
Com_show_create_event
numericGLOBAL
| SESSION
Com_show_create_table
numericGLOBAL
| SESSION
Com_show_databases
numericGLOBAL
| SESSION
Com_show_engine_logs
numericGLOBAL
| SESSION
Com_show_engine_mutex
numericGLOBAL
| SESSION
Com_show_engine_status
numericGLOBAL
| SESSION
Com_show_errors
numericGLOBAL
| SESSION
Com_show_events
numericGLOBAL
| SESSION
Com_show_fields
numericGLOBAL
| SESSION
Com_show_grants
numericGLOBAL
| SESSION
Com_show_innodb_status
numericGLOBAL
| SESSION
Com_show_keys
numericGLOBAL
| SESSION
Com_show_logs
numericGLOBAL
| SESSION
Com_show_master_status
numericGLOBAL
| SESSION
Com_show_ndb_status
numericGLOBAL
| SESSION
Com_show_new_master
numericGLOBAL
| SESSION
Com_show_open_tables
numericGLOBAL
| SESSION
Com_show_plugins
numericGLOBAL
| SESSION
Com_show_privileges
numericGLOBAL
| SESSION
Com_show_processlist
numericGLOBAL
| SESSION
Com_show_slave_hosts
numericGLOBAL
| SESSION
Com_show_slave_status
numericGLOBAL
| SESSION
Com_show_status
numericGLOBAL
| SESSION
Com_show_storage_engines
numericGLOBAL
| SESSION
Com_show_tables
numericGLOBAL
| SESSION
Com_show_triggers
numericGLOBAL
| SESSION
Com_show_variables
numericGLOBAL
| SESSION
Com_show_warnings
numericGLOBAL
| SESSION
Com_slave_start
numericGLOBAL
| SESSION
Com_slave_stop
numericGLOBAL
| SESSION
Com_stmt_close
numericGLOBAL
| SESSION
Com_stmt_execute
numericGLOBAL
| SESSION
Com_stmt_fetch
numericGLOBAL
| SESSION
Com_stmt_prepare
numericGLOBAL
| SESSION
Com_stmt_reset
numericGLOBAL
| SESSION
Com_stmt_send_long_data
numericGLOBAL
| SESSION
Com_truncate
numericGLOBAL
| SESSION
Com_unlock_tables
numericGLOBAL
| SESSION
Com_update
numericGLOBAL
| SESSION
Com_update_multi
numericGLOBAL
| SESSION
Com_xa_commit
numericGLOBAL
| SESSION
Com_xa_end
numericGLOBAL
| SESSION
Com_xa_prepare
numericGLOBAL
| SESSION
Com_xa_recover
numericGLOBAL
| SESSION
Com_xa_rollback
numericGLOBAL
| SESSION
Com_xa_start
numericGLOBAL
| SESSION
Compression
numericSESSION
Connections
numericGLOBAL
Created_tmp_disk_tables
numericGLOBAL
| SESSION
Created_tmp_files
numericGLOBAL
Created_tmp_tables
numericGLOBAL
| SESSION
Delayed_errors
numericGLOBAL
Delayed_insert_threads
numericGLOBAL
Delayed_writes
numericGLOBAL
Flush_commands
numericGLOBAL
Handler_commit
numericGLOBAL
| SESSION
Handler_delete
numericGLOBAL
| SESSION
Handler_discover
numericGLOBAL
| SESSION
Handler_prepare
numericGLOBAL
| SESSION
Handler_read_first
numericGLOBAL
| SESSION
Handler_read_key
numericGLOBAL
| SESSION
Handler_read_next
numericGLOBAL
| SESSION
Handler_read_prev
numericGLOBAL
| SESSION
Handler_read_rnd
numericGLOBAL
| SESSION
Handler_read_rnd_next
numericGLOBAL
| SESSION
Handler_rollback
numericGLOBAL
| SESSION
Handler_savepoint
numericGLOBAL
| SESSION
Handler_savepoint_rollback
numericGLOBAL
| SESSION
Handler_update
numericGLOBAL
| SESSION
Handler_write
numericGLOBAL
| SESSION
Innodb_buffer_pool_pages_data
numericGLOBAL
Innodb_buffer_pool_pages_dirty
numericGLOBAL
Innodb_buffer_pool_pages_flushed
numericGLOBAL
Innodb_buffer_pool_pages_free
numericGLOBAL
Innodb_buffer_pool_pages_latched
numericGLOBAL
Innodb_buffer_pool_pages_misc
numericGLOBAL
Innodb_buffer_pool_pages_total
numericGLOBAL
Innodb_buffer_pool_read_ahead_rnd
numericGLOBAL
Innodb_buffer_pool_read_ahead_seq
numericGLOBAL
Innodb_buffer_pool_read_requests
numericGLOBAL
Innodb_buffer_pool_reads
numericGLOBAL
Innodb_buffer_pool_wait_free
numericGLOBAL
Innodb_buffer_pool_write_requests
numericGLOBAL
Innodb_data_fsyncs
numericGLOBAL
Innodb_data_pending_fsyncs
numericGLOBAL
Innodb_data_pending_reads
numericGLOBAL
Innodb_data_pending_writes
numericGLOBAL
Innodb_data_read
numericGLOBAL
Innodb_data_reads
numericGLOBAL
Innodb_data_writes
numericGLOBAL
Innodb_data_written
numericGLOBAL
Innodb_dblwr_pages_written
numericGLOBAL
Innodb_dblwr_writes
numericGLOBAL
Innodb_log_waits
numericGLOBAL
Innodb_log_write_requests
numericGLOBAL
Innodb_log_writes
numericGLOBAL
Innodb_os_log_fsyncs
numericGLOBAL
Innodb_os_log_pending_fsyncs
numericGLOBAL
Innodb_os_log_pending_writes
numericGLOBAL
Innodb_os_log_written
numericGLOBAL
Innodb_page_size
numericGLOBAL
Innodb_pages_created
numericGLOBAL
Innodb_pages_read
numericGLOBAL
Innodb_pages_written
numericGLOBAL
Innodb_row_lock_current_waits
numericGLOBAL
Innodb_row_lock_time
numericGLOBAL
Innodb_row_lock_time_avg
numericGLOBAL
Innodb_row_lock_time_max
numericGLOBAL
Innodb_row_lock_waits
numericGLOBAL
Innodb_rows_deleted
numericGLOBAL
Innodb_rows_inserted
numericGLOBAL
Innodb_rows_read
numericGLOBAL
Innodb_rows_updated
numericGLOBAL
Key_blocks_not_flushed
numericGLOBAL
Key_blocks_unused
numericGLOBAL
Key_blocks_used
numericGLOBAL
Key_read_requests
numericGLOBAL
Key_reads
numericGLOBAL
Key_write_requests
numericGLOBAL
Key_writes
numericGLOBAL
Last_query_cost
numericSESSION
Max_used_connections
numericGLOBAL
Ndb_cluster_node_id
numericGLOBAL
| SESSION
Ndb_config_from_host
numericGLOBAL
| SESSION
Ndb_config_from_port
numericGLOBAL
| SESSION
ndb-nodeid
numericGLOBAL
Not_flushed_delayed_rows
numericGLOBAL
Open_files
numericGLOBAL
Open_streams
numericGLOBAL
Open_tables
numericGLOBAL
| SESSION
Opened_tables
numericGLOBAL
| SESSION
Prepared_stmt_count
numericGLOBAL
Qcache_free_blocks
numericGLOBAL
Qcache_free_memory
numericGLOBAL
Qcache_hits
numericGLOBAL
Qcache_inserts
numericGLOBAL
Qcache_lowmem_prunes
numericGLOBAL
Qcache_not_cached
numericGLOBAL
Qcache_queries_in_cache
numericGLOBAL
Qcache_total_blocks
numericGLOBAL
Queries
numericGLOBAL
| SESSION
Questions
numericGLOBAL
| SESSION
Rpl_status
stringGLOBAL
Select_full_join
numericGLOBAL
| SESSION
Select_full_range_join
numericGLOBAL
| SESSION
Select_range
numericGLOBAL
| SESSION
Select_range_check
numericGLOBAL
| SESSION
Select_scan
numericGLOBAL
| SESSION
Slave_open_temp_tables
numericGLOBAL
Slave_retried_transactions
numericGLOBAL
Slave_running
booleanGLOBAL
Slow_launch_threads
numericGLOBAL
| SESSION
Slow_queries
numericGLOBAL
| SESSION
Sort_merge_passes
numericGLOBAL
| SESSION
Sort_range
numericGLOBAL
| SESSION
Sort_rows
numericGLOBAL
| SESSION
Sort_scan
numericGLOBAL
| SESSION
Ssl_accept_renegotiates
numericGLOBAL
Ssl_accepts
numericGLOBAL
Ssl_callback_cache_hits
numericGLOBAL
Ssl_cipher
stringGLOBAL
| SESSION
Ssl_cipher_list
stringGLOBAL
| SESSION
Ssl_client_connects
numericGLOBAL
Ssl_connect_renegotiates
numericGLOBAL
Ssl_ctx_verify_depth
numericGLOBAL
Ssl_ctx_verify_mode
numericGLOBAL
Ssl_default_timeout
numericGLOBAL
| SESSION
Ssl_finished_accepts
numericGLOBAL
Ssl_finished_connects
numericGLOBAL
Ssl_session_cache_hits
numericGLOBAL
Ssl_session_cache_misses
numericGLOBAL
Ssl_session_cache_mode
stringGLOBAL
Ssl_session_cache_overflows
numericGLOBAL
Ssl_session_cache_size
numericGLOBAL
Ssl_session_cache_timeouts
numericGLOBAL
Ssl_sessions_reused
numericGLOBAL
| SESSION
Ssl_used_session_cache_entries
numericGLOBAL
Ssl_verify_depth
numericGLOBAL
| SESSION
Ssl_verify_mode
numericGLOBAL
| SESSION
Ssl_version
stringGLOBAL
| SESSION
Table_locks_immediate
numericGLOBAL
Table_locks_waited
numericGLOBAL
Tc_log_max_pages_used
numericGLOBAL
Tc_log_page_size
numericGLOBAL
Tc_log_page_waits
numericGLOBAL
Threads_cached
numericGLOBAL
Threads_connected
numericGLOBAL
Threads_created
numericGLOBAL
Threads_running
numericGLOBAL
Uptime
numericGLOBAL
Uptime_since_flush_status
numericGLOBAL
The status variables have the following meanings. For meanings of status variables specific to MySQL Cluster, see Section 17.3.4.4, “MySQL Cluster Status Variables”.
Aborted_clients
The number of connections that were aborted because the client died without closing the connection properly. SeeSection C.5.2.11, “Communication Errors and Aborted Connections”.
Aborted_connects
The number of failed attempts to connect to the MySQL server. See Section C.5.2.11, “Communication Errors and Aborted Connections”.
Binlog_cache_disk_use
The 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_use
The number of transactions that used the temporary binary log cache.
Bytes_received
The number of bytes received from all clients.
Bytes_sent
The number of bytes sent to all clients.
Com_
xxx
The
Com_
statement counter variables indicate the number of times eachxxx
xxx
statement has been executed. There is one status variable for each type of statement. For example,Com_delete
andCom_insert
countDELETE
andINSERT
statements, respectively. However, if a query result is returned from query cache, the server increments theQcache_hits
status variable, notCom_select
. See Section 8.6.3.4, “Query Cache Status and Maintenance”.All of the
Com_stmt_
variables are increased even if a prepared statement argument is unknown or an error occurred during execution. In other words, their values correspond to the number of requests issued, not to the number of requests successfully completed.xxx
The
Com_stmt_
status variables were added in 5.0.8:xxx
Com_stmt_prepare
Com_stmt_execute
Com_stmt_fetch
Com_stmt_send_long_data
Com_stmt_reset
Com_stmt_close
Those variables stand for prepared statement commands. Their names refer to the
COM_
command set used in the network layer. In other words, their values increase whenever prepared statement API calls such asmysql_stmt_prepare(), mysql_stmt_execute(), and so forth are executed. However,xxx
Com_stmt_prepare
,Com_stmt_execute
andCom_stmt_close
also increase forPREPARE
,EXECUTE
, orDEALLOCATE PREPARE
, respectively. Additionally, the values of the older statement counter variablesCom_prepare_sql
,Com_execute_sql
, andCom_dealloc_sql
increase for thePREPARE
,EXECUTE
, andDEALLOCATE PREPARE
statements.Com_stmt_fetch
stands for the total number of network round-trips issued when fetching from cursors.Compression
Whether the client connection uses compression in the client/server protocol. Added in MySQL 5.0.16.
Connections
The number of connection attempts (successful or not) to the MySQL server.
Created_tmp_disk_tables
The number of internal on-disk temporary tables created by the server while executing statements.
If an internal temporary table is created initially as an in-memory table but becomes too large, MySQL automatically converts it to an on-disk table. The maximum size for in-memory temporary tables is the minimum of the
tmp_table_size
andmax_heap_table_size
values. IfCreated_tmp_disk_tables
is large, you may want to increase thetmp_table_size
ormax_heap_table_size
values. value to lessen the likelihood that internal temporary tables in memory will be converted to on-disk tables.You can compare the number of internal on-disk temporary tables created to the total number of internal temporary tables created by comparing the values of the
Created_tmp_disk_tables
andCreated_tmp_tables
variables.See also Section 8.8.5, “How MySQL Uses Internal Temporary Tables”.
Created_tmp_files
How many temporary files mysqld has created.
Created_tmp_tables
The number of internal temporary tables created by the server while executing statements.
You can compare the number of internal on-disk temporary tables created to the total number of internal temporary tables created by comparing the values of the
Created_tmp_disk_tables
andCreated_tmp_tables
variables.See also Section 8.8.5, “How MySQL Uses Internal Temporary Tables”.
Delayed_errors
The number of rows written with
INSERT DELAYED
for which some error occurred (probablyduplicate key
).Delayed_insert_threads
The number of
INSERT DELAYED
handler threads in use.Delayed_writes
The number of
INSERT DELAYED
rows written.Flush_commands
The number of times the server flushes tables, whether because a user executed a
FLUSH TABLES
statement or due to internal server operation. It is also incremented by receipt of aCOM_REFRESH
packet. This is in contrast toCom_flush
, which indicates how manyFLUSH
statements have been executed, whetherFLUSH TABLES
,FLUSH LOGS
, and so forth.Handler_commit
The number of internal
COMMIT
statements.Handler_delete
The number of times that rows have been deleted from tables.
Handler_prepare
A counter for the prepare phase of two-phase commit operations. Added in MySQL 5.0.3.
Handler_read_first
The number of times the first entry in an index was read. If this value is high, it suggests that the server is doing a lot of full index scans; for example,
SELECT col1 FROM foo
, assuming thatcol1
is indexed.Handler_read_key
The number of requests to read a row based on a key. If this value is high, it is a good indication that your tables are properly indexed for your queries.
Handler_read_next
The number of requests to read the next row in key order. This value is incremented if you are querying an index column with a range constraint or if you are doing an index scan.
Handler_read_prev
The number of requests to read the previous row in key order. This read method is mainly used to optimize
ORDER BY ... DESC
.Handler_read_rnd
The number of requests to read a row based on a fixed position. This 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 do not use keys properly.
Handler_read_rnd_next
The number of requests to read the next row in the data file. This value 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_rollback
The number of requests for a storage engine to perform a rollback operation.
Handler_savepoint
The number of requests for a storage engine to place a savepoint. Added in MySQL 5.0.3.
Handler_savepoint_rollback
The number of requests for a storage engine to roll back to a savepoint. Added in MySQL 5.0.3.
Handler_update
The number of requests to update a row in a table.
Handler_write
The number of requests to insert a row in a table.
Innodb_buffer_pool_pages_data
The number of pages containing data (dirty or clean). Added in MySQL 5.0.2.
Innodb_buffer_pool_pages_dirty
The number of pages currently dirty. Added in MySQL 5.0.2.
Innodb_buffer_pool_pages_flushed
The number of buffer pool page-flush requests. Added in MySQL 5.0.2.
Innodb_buffer_pool_pages_free
The number of free pages. Added in MySQL 5.0.2.
Innodb_buffer_pool_pages_latched
The number of latched pages in
InnoDB
buffer pool. These are pages currently being read or written or that cannot be flushed or removed for some other reason. Added in MySQL 5.0.2. Calculation of this variable is expensive, so as of MySQL 5.0.68, it is available only when theUNIV_DEBUG
system is defined at server build time.Innodb_buffer_pool_pages_misc
The number of pages that are 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
. Added in MySQL 5.0.2.Innodb_buffer_pool_pages_total
The total size of buffer pool, in pages. Added in MySQL 5.0.2.
Innodb_buffer_pool_read_ahead_rnd
The number of “random” read-aheads initiated by
InnoDB
. This happens when a query scans a large portion of a table but in random order. Added in MySQL 5.0.2.Innodb_buffer_pool_read_ahead_seq
The number of sequential read-aheads initiated by
InnoDB
. This happens whenInnoDB
does a sequential full table scan. Added in MySQL 5.0.2.Innodb_buffer_pool_read_requests
The number of logical read requests
InnoDB
has done. Added in MySQL 5.0.2.Innodb_buffer_pool_reads
The number of logical reads that
InnoDB
could not satisfy from the buffer pool, and had to read directly from the disk.Innodb_buffer_pool_wait_free
Normally, writes to the
InnoDB
buffer pool happen in the background. However, if it is necessary to read or create a page and no clean pages are available, it is also necessary to wait for pages to be flushed first. This counter counts instances of these waits. If the buffer pool size has been set properly, this value should be small. Added in MySQL 5.0.2.Innodb_buffer_pool_write_requests
The number writes done to the
InnoDB
buffer pool. Added in MySQL 5.0.2.Innodb_data_fsyncs
The number of
fsync()
operations so far. Added in MySQL 5.0.2.Innodb_data_pending_fsyncs
The current number of pending
fsync()
operations. Added in MySQL 5.0.2.Innodb_data_pending_reads
The current number of pending reads. Added in MySQL 5.0.2.
Innodb_data_pending_writes
The current number of pending writes. Added in MySQL 5.0.2.
Innodb_data_read
The amount of data read since the server was started. Added in MySQL 5.0.2.
Innodb_data_reads
The total number of data reads. Added in MySQL 5.0.2.
Innodb_data_writes
The total number of data writes. Added in MySQL 5.0.2.
Innodb_data_written
The amount of data written so far, in bytes. Added in MySQL 5.0.2.
Innodb_dblwr_pages_written
The number of pages that have been written for doublewrite operations. Added in MySQL 5.0.2. SeeSection 14.2.11.1, “
InnoDB
Disk I/O”.Innodb_dblwr_writes
The number of doublewrite operations that have been performed. Added in MySQL 5.0.2. See Section 14.2.11.1, “
InnoDB
Disk I/O”.Innodb_log_waits
The number of times that the log buffer was too small and a wait was required for it to be flushed before continuing. Added in MySQL 5.0.2.
Innodb_log_write_requests
The number of log write requests. Added in MySQL 5.0.2.
Innodb_log_writes
The number of physical writes to the log file. Added in MySQL 5.0.2.
Innodb_os_log_fsyncs
The number of
fsync()
writes done to the log file. Added in MySQL 5.0.2.Innodb_os_log_pending_fsyncs
The number of pending log file
fsync()
operations. Added in MySQL 5.0.2.Innodb_os_log_pending_writes
The number of pending log file writes. Added in MySQL 5.0.2.
Innodb_os_log_written
The number of bytes written to the log file. Added in MySQL 5.0.2.
Innodb_page_size
The compiled-in
InnoDB
page size (default 16KB). Many values are counted in pages; the page size permits them to be easily converted to bytes. Added in MySQL 5.0.2.Innodb_pages_created
The number of pages created. Added in MySQL 5.0.2.
Innodb_pages_read
The number of pages read. Added in MySQL 5.0.2.
Innodb_pages_written
The number of pages written. Added in MySQL 5.0.2.
Innodb_row_lock_current_waits
The number of row locks currently being waited for. Added in MySQL 5.0.3.
Innodb_row_lock_time
The total time spent in acquiring row locks, in milliseconds. Added in MySQL 5.0.3.
Innodb_row_lock_time_avg
The average time to acquire a row lock, in milliseconds. Added in MySQL 5.0.3.
Innodb_row_lock_time_max
The maximum time to acquire a row lock, in milliseconds. Added in MySQL 5.0.3.
Innodb_row_lock_waits
The number of times a row lock had to be waited for. Added in MySQL 5.0.3.
Innodb_rows_deleted
The number of rows deleted from
InnoDB
tables. Added in MySQL 5.0.2.Innodb_rows_inserted
The number of rows inserted into
InnoDB
tables. Added in MySQL 5.0.2.Innodb_rows_read
The number of rows read from
InnoDB
tables. Added in MySQL 5.0.2.Innodb_rows_updated
The number of rows updated in
InnoDB
tables. Added in MySQL 5.0.2.Key_blocks_not_flushed
The number of key blocks in the key cache that have changed but have not yet been flushed to disk.
Key_blocks_unused
The number of unused blocks in the key cache. You can use this value to determine how much of the key cache is in use; see the discussion of
key_buffer_size
in Section 5.1.4, “Server System Variables”.Key_blocks_used
The 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_requests
The number of requests to read a key block from the cache.
Key_reads
The number of physical reads of a key block from disk. If
Key_reads
is large, then yourkey_buffer_size
value is probably too small. The cache miss rate can be calculated asKey_reads
/Key_read_requests
.Key_write_requests
The number of requests to write a key block to the cache.
Key_writes
The number of physical writes of a key block to disk.
Last_query_cost
The total cost of the last compiled query as computed by the query optimizer. This is 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. This variable was added in MySQL 5.0.1, with a default value of -1. In MySQL 5.0.7, the default was changed to 0; also in version 5.0.7, the scope of
Last_query_cost
was changed to session rather than global.The
Last_query_cost
value can be computed accurately only for simple “flat” queries, not complex queries such as those with subqueries orUNION
. For the latter, the value is set to 0.Prior to MySQL 5.0.16, this variable was not updated for queries served from the query cache.
Max_used_connections
The maximum number of connections that have been in use simultaneously since the server started.
Not_flushed_delayed_rows
The number of rows waiting to be written in
INSERT DELAYED
queues.Open_files
The number of files that are open. This count includes regular files opened by the server. It does not include other types of files such as sockets or pipes. Also, the count does not include files that storage engines open using their own internal functions rather than asking the server level to do so.
Open_streams
The number of streams that are open (used mainly for logging).
Open_tables
The number of tables that are open.
Opened_tables
The number of tables that have been opened. If
Opened_tables
is big, yourtable_cache
value is probably too small.Prepared_stmt_count
The current number of prepared statements. (The maximum number of statements is given by the
max_prepared_stmt_count
system variable.) This variable was added in MySQL 5.0.32.Qcache_free_blocks
The number of free memory blocks in the query cache.
Qcache_free_memory
The amount of free memory for the query cache.
Qcache_hits
The number of query cache hits.
Qcache_inserts
The number of queries added to the query cache.
Qcache_lowmem_prunes
The number of queries that were deleted from the query cache because of low memory.
Qcache_not_cached
The number of noncached queries (not cacheable, or not cached due to the
query_cache_type
setting).Qcache_queries_in_cache
The number of queries registered in the query cache.
Qcache_total_blocks
The total number of blocks in the query cache.
Queries
The number of statements executed by the server. This variable includes statements executed within stored programs, unlike the
Questions
variable. It does not countCOM_PING
orCOM_STATISTICS
commands. This variable was added in MySQL 5.0.76.Questions
The number of statements executed by the server. As of MySQL 5.0.72, this includes only statements sent to the server by clients and no longer includes statements executed within stored programs, unlike the
Queries
variable. This variable does not countCOM_PING
,COM_STATISTICS
,COM_STMT_PREPARE
,COM_STMT_CLOSE
, orCOM_STMT_RESET
commands.Rpl_status
The status of fail-safe replication (not implemented). This variable is unused and is removed in MySQL 5.6.
Select_full_join
The number of joins that perform table scans because they do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.
Select_full_range_join
The number of joins that used a range search on a reference table.
Select_range
The number of joins that used ranges on the first table. This is normally not a critical issue even if the value is quite large.
Select_range_check
The 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_scan
The number of joins that did a full scan of the first table.
Slave_open_temp_tables
The number of temporary tables that the slave SQL thread currently has open. If the value is greater than zero, it is not safe to shut down the slave; see Section 16.4.1.15, “Replication and Temporary Tables”.
Slave_retried_transactions
The total number of times since startup that the replication slave SQL thread has retried transactions. This variable was added in version 5.0.4.
Slave_running
This is
ON
if this server is a replication slave that is connected to a replication master, and both the I/O and SQL threads are running; otherwise, it isOFF
.Slow_launch_threads
The number of threads that have taken more than
slow_launch_time
seconds to create.Slow_queries
The number of queries that have taken more than
long_query_time
seconds. See Section 5.2.4, “The Slow Query Log”.Sort_merge_passes
The number of merge passes that 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_range
The number of sorts that were done using ranges.
Sort_rows
The number of sorted rows.
Sort_scan
The number of sorts that were done by scanning the table.
Ssl_accept_renegotiates
The number of negotiates needed to establish the connection.
Ssl_accepts
The number of accepted SSL connections.
Ssl_callback_cache_hits
The number of callback cache hits.
Ssl_cipher
The current SSL cipher (empty for non-SSL connections).
Ssl_cipher_list
The list of possible SSL ciphers.
Ssl_client_connects
The number of SSL connection attempts to an SSL-enabled master.
Ssl_connect_renegotiates
The number of negotiates needed to establish the connection to an SSL-enabled master.
Ssl_ctx_verify_depth
The SSL context verification depth (how many certificates in the chain are tested).
Ssl_ctx_verify_mode
The SSL context verification mode.
Ssl_default_timeout
The default SSL timeout.
Ssl_finished_accepts
The number of successful SSL connections to the server.
Ssl_finished_connects
The number of successful slave connections to an SSL-enabled master.
Ssl_session_cache_hits
The number of SSL session cache hits.
Ssl_session_cache_misses
The number of SSL session cache misses.
Ssl_session_cache_mode
The SSL session cache mode.
Ssl_session_cache_overflows
The number of SSL session cache overflows.
Ssl_session_cache_size
The SSL session cache size.
Ssl_session_cache_timeouts
The number of SSL session cache timeouts.
Ssl_sessions_reused
How many SSL connections were reused from the cache.
Ssl_used_session_cache_entries
How many SSL session cache entries were used.
Ssl_verify_depth
The verification depth for replication SSL connections.
Ssl_verify_mode
The verification mode for replication SSL connections.
Ssl_version
The SSL protocol version of the connection.
Table_locks_immediate
The number of times that a request for a table lock could be granted immediately.
Table_locks_waited
The number of times that a request for a table lock could not be granted 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.
Tc_log_max_pages_used
For the memory-mapped implementation of the log that is used by mysqld when it acts as the transaction coordinator for recovery of internal XA transactions, this variable indicates the largest number of pages used for the log since the server started. If the product of
Tc_log_max_pages_used
andTc_log_page_size
is always significantly less than the log size, the size is larger than necessary and can be reduced. (The size is set by the--log-tc-size
option. Currently, this variable is unused: It is unneeded for binary log-based recovery, and the memory-mapped recovery log method is not used unless the number of storage engines capable of two-phase commit is greater than one. (InnoDB
is the only applicable engine.) Added in MySQL 5.0.3.Tc_log_page_size
The page size used for the memory-mapped implementation of the XA recovery log. The default value is determined using
getpagesize()
. Currently, this variable is unused for the same reasons as described forTc_log_max_pages_used
. Added in MySQL 5.0.3.Tc_log_page_waits
For the memory-mapped implementation of the recovery log, this variable increments each time the server was not able to commit a transaction and had to wait for a free page in the log. If this value is large, you might want to increase the log size (with the
--log-tc-size
option). For binary log-based recovery, this variable increments each time the binary log cannot be closed because there are two-phase commits in progress. (The close operation waits until all such transactions are finished.) Added in MySQL 5.0.3.Threads_cached
The number of threads in the thread cache.
Threads_connected
The number of currently open connections.
Threads_created
The number of threads created to handle connections. If
Threads_created
is big, you may want to increase thethread_cache_size
value. The cache miss rate can be calculated asThreads_created
/Connections
.Threads_running
The number of threads that are not sleeping.
Uptime
The number of seconds that the server has been up.
Uptime_since_flush_status
The number of seconds since the most recent
FLUSH STATUS
statement. This variable was added in 5.0.35. (MySQL Community only)
- 5.1.6. Server Status Variables
- 5.1.6 Server Status Variables
- mysql---Server Status Variables
- MySQL 状态变量(Server Status Variables)
- THE HANDLER_READ_* STATUS VARIABLES
- MySQL的variables和status
- MySQL Select and Sort Status Variables
- mysql之status和variables区别
- MySql之show status、show variables
- mysql结合status和variables 优化mysql
- mysql的 show status 和 show variables
- mysql之status和variables区别及用法详解
- Mysql 5.7 information_schema 的status和variables表deprecated
- mysql之status和variables区别及用法详解
- 开启 Apache Server Status
- apache server-status
- [OpenStack]Server status values
- MySQL - 翻译 - 5.1 Reference Manual参考手册 - 5.1.3 Server System Variables服务器系统变量 - max_heap_table_size
- 简单排序算法实现——希尔排序
- TFTP/NFS/Samba
- PL-SQL Developer 整合SVN Pluglns
- Java虚拟机方法区
- SP报错内容:此查询使用不支持的元素,例如引用多个列表,或使用 EntityRef/EntitySet 投影完整实体
- 5.1.6. Server Status Variables
- C++动态加载 DLL
- ubuntu12.04中安装lamp
- solr 4.1入门官方文档
- Linux中find常见用法示例
- 教你如何预防DdoS攻击
- Comet:基于 HTTP 的long-polling技术
- i-jetty-3.1编译总结
- C++还未有甚解的东西!
User Comments
Posted by Demetrios Stavrinos on July 22 2004 12:27pm[Delete] [Edit]Reading the explanation for Handler read rnd next , I question it! I list some number from a test db that does almost all accesses by locating a record with a key (GE or xxx%) and then using next to access related record; yet the Handler read rnd next is relatively large.
Posted by Heikki Hannikainen on April 28 2006 10:23am[Delete] [Edit]Handler read key 42053
Handler read next 453703
Handler read rnd 696
Handler read rnd next 104378
On MySQL 5.0 the com_* variables of 'show status' are counted for the current connection only. The new undocumented command 'show global status' shows server-wide counters. (http://bugs.mysql.com/bug.php?id=19422)
Posted by sheila yao on April 16 2007 9:23pm[Delete] [Edit]In version 4.0.17, the explanation to Handler_ is different:
Posted by Roel Van de Paar on September 21 2009 4:34am[Delete] [Edit]Example:
Handler_delete:
The number of times a row was deleted from a table.
Handler_update
The number of requests to update a row in a table.
Handler_write
The number of requests to insert a row in a table.
Could this be a typo for Handler_delete? Because requests and rows updated/deleted/inserted are different concept.
Sheila
There's a bug in 5.0.36 (and likely surrounding versions) for Handler_write: it increases by one every time a row from SHOW STATUS is displayed:
1 row in set (0.00 sec)------
mysql> FLUSH STATUS;
Query OK, 0 rows affected (0.00 sec)
mysql> SHOW GLOBAL STATUS; SHOW SESSION STATUS;
[...] 224 rows in set (0.01 sec)
[...] 224 rows in set (0.01 sec)
mysql> SHOW SESSION STATUS LIKE 'Handler_write';
------
Given the bug for Handler_write it is not possible to find out how many rows were inserted in this version, unless you use a workaround:
Rows_inserted= Handler_write - (number of times SHOW STATUS was run * number of rows SHOW STATUS displayed)
This could be programmed further using the Com_show_status variable:
--------
mysql> SHOW SESSION STATUS LIKE 'Com_show_status';
1 row in set (0.00 sec)
--------
So, on a system/version that had 224 rows in SHOW STATUS (please check), the workaround formula would be:
Rows_inserted=Handler_write-(Com_show_status * 224)
Note though that this workaround does not work when using partial SHOW STATUS statements (using LIKE etc) from time to time.