MySQL Show Status Command parameters

Source: Internet
Author: User

Aborted_clients the number of connections that have been discarded because the client did not properly close the connection already dead. Aborted_connects the number of times the connection to the MySQL server has failed. Binlog_cache_disk_use when the transaction log is larger than binlog_cache_size, he creates a temporary file that indicates how many transactions used the temporary file Binlog_cache_use indicates how many things use Binlog_cache_size to cache uncommitted log of things bytes_received the number of bytes that have been received from the customer. Bytes_sent the number of bytes that have been sent to all customers. Com_[statement] One of these variables for each statement. The value of the variable indicates the number of times the statement was executed, such as Com_select, indicating the number of times the query statement was executed. Connections the number of attempts to connect to the MySQL server. Created_tmp_disk_tables the number of temporary tables that are automatically created on the hard disk when the server executes the statement Created_tmp_tables the number of suppressed temporary tables that have been created when the statement is executed. Created_tmp_files mysqld The number of temporary files created Delayed_insert_threads the number of deferred plug-in processor threads being used. Delayed_writes the number of rows written with the insert Delayed. Delayed_errors the number of rows written with insert Delayed for some errors (possibly repeating key values). Flush_commands the number of times the flush command was executed. Handler_commit number of internal commit commands Handler_delete the number of times a row was requested to be deleted from a table. Handler_discover MySQL server can ask NDB cluster whether the storage engine knows the table of a certain name. This is called discovery. Handler_discover describes the number of times that this method was discovered. Handler_prepare The number of times the Handler_read_first request reads the first row in the table. The Handler_read_key requests a number based on the key read line. If the index is working, the value of the Handler_read_key will be high, which represents the number of times a row is read by the index value, and a low value indicates that the performance improvement of the index is not very good because the index is not used frequently. The number of times a handler_read_next request reads into a row based on one key. The number of times a HANDLER_READ_RND request reads into a row based on a fixed position. Handler_read_rnd_next the number of requests to read the next row of data in the data file. Generally, this value cannot be too high because this means that the query operation does not use the index and must be read from the data file Handler_read_prev the number of requests to read the previous row of data in the order in which they are indexed. This variable value is used by a statement of the Select FieldList ORDER by fields desc type Handler_rollback number of internal rollback commands Handler_savepoint the number of requests to place a savepoint in a storage engine handler_savepoint_rollback the requirement of a storage engine to roll back to a save point Handler_update the number of times a row in the table was requested to be updated. The number of times the Handler_write request inserts a row into the table. Innodb_buffer_pool_pages_data contains the number of pages (dirty or clean) of the data. Innodb_buffer_pool_pages_dirty the current number of dirty pages. innodb_buffer_pool_pages_flushed the number of buffer pool pages required to be emptied. Innodb_buffer_pool_pages_free empty pages. Innodb_buffer_pool_pages_misc busy pages because they have been assigned precedence for administration, such as row locking or applicable hash indexes. The 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_total Total buffer pool size (pages). Innodb_buffer_pool_read_ahead_rnd Innodb The number of "random" read-aheads initialized. Occurs when the query scans a large part of a table in a random order. Innodb_buffer_pool_read_ahead_seq Innodb the number of sequential read-aheads initialized. Occurs when InnoDB performs a sequential full-table scan. Innodb_buffer_pool_read_requests Innodb The number of logical read requests that have been completed. The innodb_buffer_pool_reads cannot satisfy the logical read count in a buffer pool that Innodb must read in a single page. Innodb_buffer_pool_wait_free General, write to the INNODB buffer pool through the background. However, if you need to read or create a page, and there is no clean page available, it also needs to wait for the page to empty first. The counter counts the waiting instance. If the buffer pool size is already set appropriately, the value should be small. Innodb_buffer_pool_write_requests the number of writes to the INNODB buffer pool. Innodb_data_fsyncs Fsync () operand. Innodb_data_pending_fsyncs the number of Fsync () operands currently pending. Innodb_data_pending_reads the current pending reading. Innodb_data_pending_writes the current number of pending writes. Innodb_data_read the number of data (bytes) that have been read to this point. Innodb_data_reads The total number of data reads. Innodb_data_writes The total number of data writes. Innodb_data_written The amount of data (bytes) that has been written to this point. Innodb_dblwr_writes, Innodb_dblwr_pages_written the number of double write operations that have been performed and the pages that have been written for this purpose. See section 15.2, 14.1, "Disk I/O". Innodb_log_waits we have to wait for the time, because the log buffer is too small, we must wait for it to be emptied before proceeding. Innodb_log_write_requests the number of log write requests. Innodb_log_writes the number of physical writes to the log file. Innodb_os_log_fsyncs the number of Fsync () writes completed to the log file. Innodb_os_log_pending_fsyncs the number of pending log file Fsync () operations. Innodb_os_log_pending_writes a pending log file write operation. Innodb_os_log_written the number of bytes written to the log file. Innodb_page_size compiled Innodb page size (default 16KB). Many values are counted in pages, and the size of the page is easily converted to bytes. innodb_pages_created the number of pages created. The number of pages read by Innodb_pages_read. Number of pages written by Innodb_pages_written. Innodb_row_lock_current_waits the number of rows currently waiting to be locked. Innodb_row_lock_time the total time, in milliseconds, that the row lock takes. Innodb_row_lock_time_avg the average time, in milliseconds, that the row is locked. Innodb_row_lock_time_max the maximum time, in milliseconds, that a row is locked. Innodb_row_lock_waits the number of times a row lock must wait. innodb_rows_deleted number of rows deleted from the Innodb table innodb_rows_inserted the number of rows inserted into the Innodb table. Innodb_rows_read the number of rows read from the Innodb table. innodb_rows_updated the number of rows updated in the Innodb table. The number of data blocks in the Key_blocks_not_flushed key cache that have been changed but have not yet been emptied to the hard disk. The number of unused blocks in the key_blocks_unused key cache. You can use this value to determine how many key caches are used, as described in Section 5.3.3, "Server System Variables" in Key_buffer_size. The number of blocks used in the key_blocks_used key cache. The value is a high-level line marker that shows how many blocks have been used at the same time. Key_read_requests the number of requests from the cache to read the data block of the key. Key_reads the number of times the key's data block was read from the hard disk. If the key_reads is large, the Key_buffer_size value may be too small. You can calculate the cache loss rate with key_reads/key_read_requests. Key_write_requests the number of requests to write the key's data block to the cache. Key_writes the number of times the physical write operation of the data block to which the key was written to the hard disk. Last_query_cost the total cost of the last compiled query computed with the query optimizer. Used to compare the cost of different query scenarios for the same query. The default value of 0 indicates that the query has not been compiled. The default value is 0. Last_query_cost has a session scope. Max_used_connections the maximum number of connections that have been used at the same time since the server started. Not_flushed_delayed_rows the number of rows waiting to be written to the Insert delay queue. Open_files the number of open files. Open_streams the number of open streams (primarily for logging). Open_table_definitions Open_tables the number of tables currently open. Opened_files Opened_table_definitions Opened_tables the number of tables that have been opened. If the opened_tables is larger, the Table_cache value may be too small. Prepared_stmt_count the number of current Prepared statements, the maximum number will be controlled by the variable max_prepared_stmt_count, when deallocate prepare, change the state value will be reduced Qcache_free_blocks the number of free memory blocks in the query cache. Qcache_free_memory The amount of free memory used to query the cache. Qcache_hits the number of times the query cache was accessed. Qcache_inserts the number of queries added to the cache. Qcache_lowmem_prunes the number of queries that are removed from the cache because of less memory. qcache_not_cached number of non-cached queries (not cacheable, or because Query_cache_type setpoint is not cached). Qcache_queries_in_cache the number of queries registered in the cache. Qcache_total_blocks the total number of blocks in the query cache. Queries the number of statements executed by the server, including statements in stored procedures, including show status Questions the number of queries destined for the server. Rpl_status the state of full replication (this variable is only used in versions after MySQL 4). Select_full_join the number of joins that do not use an index. If the value is not 0, you should double-check the index of the table. Select_full_range_join the number of joins that use a range search in the referenced table. Select_range the number of joins that use a range in the first table. The general situation is not a critical issue, even if the value is quite large. Select_range_check the number of joins without a key value that are checked for key values after each row of data. If it is not 0, you should carefully check the index of the table. Select_scan the number of joins that perform a full scan of the first table. Slave_open_temp_tables the number of temporary tables currently open from SQL threads. slave_running If the server is a slave server that is connected to the primary server, the value is on. Slave_retried_transactions The total number of attempts to replicate from the server SQL thread after startup. Slow_launch_threads the number of threads that have created longer than slow_launch_time seconds. Slow_queries the number of queries that have been queried for more than long_query_time seconds. See section 5.11, 4, "Slow query log". Sort_merge_passes the number of merges that the sorting algorithm has performed. If the value of this variable is large, you should consider increasing the value of the sort_buffer_size system variable. Sort_range the number of sorts that are executed within the range. Sort_rows the number of rows that have been sorted. Sort_scan the number of sorting completed by the scan table. Table_locks_immediate the number of times a table lock was immediately obtained. table_locks_waited the number of times a table lock cannot be obtained immediately. If the value is high and there is a performance problem, you should first refine the query and then split the table or use replication. tc_log_max_pages_used tc_log_page_size tc_log_page_waits threads_cached Thread Cache value threads_connected the number of connections currently open Threads_ Created creates the number of threads used to process the connection. If the threads_created is larger, you may want to increase the thread_cache_size value. Calculation method for cache access rate threads_created (new thread)/connections (incremented if thread connection) threads_running the number of active (non-sleep) threads Uptime the time (in seconds) that the server has been running Uptime_since_flush_status the last time the flush status was used (in seconds Ssl_xxx the variables used for SSL connections.

MySQL Show Status Command parameters

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.