mysql server status variables Flashcards
(195 cards)
1
Q
Aborted_clients
A
The number of connections that were aborted because the client died without closing the connection properly. SeeSectionC.5.2.11 “Communication Errors and Aborted Connections”.
2
Q
Aborted_connects
A
The number of failed attempts to connect to the MySQL server. SeeSectionC.5.2.11 “Communication Errors and Aborted Connections”.
For additional connection-related information check theConnection_errors_xxxstatus variables and thehost_cachetable.
3
Q
Binlog_cache_disk_use
A
The number of transactions that used the temporary binary log cache but that exceeded the value ofbinlog_cache_sizeand used a temporary file to store statements from the transaction.
The number of nontransactional statements that caused the binary log transaction cache to be written to disk is tracked separately in theBinlog_stmt_cache_disk_usestatus variable.
4
Q
Binlog_cache_use
A
The number of transactions that used the binary log cache.
5
Q
Binlog_stmt_cache_disk_use
A
The number of nontransaction statements that used the binary log statement cache but that exceeded the value ofbinlog_stmt_cache_sizeand used a temporary file to store those statements.
6
Q
Binlog_stmt_cache_use
A
The number of nontransactional statements that used the binary log statement cache.
7
Q
Bytes_received
A
The number of bytes received from all clients.
8
Q
Bytes_sent
A
The number of bytes sent to all clients.
9
Q
Com_xxx
A
The Com_xxx statement counter variables indicate the number of times each xxx statement has been executed. There is one status variable for each type of statement. For example Com_delete and Com_update count DELETE and UPDATE statements respectively. Com_delete_multi and Com_update_multi are similar but apply to DELETE and UPDATE statements that use multiple-table syntax.
If a query result is returned from query cache the server increments the Qcache_hits status variable not Com_select. See Section 8.9.3.4 “Query Cache Status and Maintenance”.
All of the Com_stmt_xxx 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.
The Com_stmt_xxx status variables are as follows:
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_xxx command set used in the network layer. In other words their values increase whenever prepared statement API calls such as mysql_stmt_prepare() mysql_stmt_execute() and so forth are executed. However Com_stmt_prepare Com_stmt_execute and Com_stmt_close also increase for PREPARE EXECUTE or DEALLOCATE PREPARE respectively. Additionally the values of the older statement counter variables Com_prepare_sql Com_execute_sql and Com_dealloc_sql increase for the PREPARE EXECUTE and DEALLOCATE PREPARE statements. Com_stmt_fetch stands for the total number of network round-trips issued when fetching from cursors.
Com_stmt_reprepare indicates the number of times statements were automatically reprepared by the server after metadata changes to tables or views referred to by the statement. A reprepare operation increments Com_stmt_reprepare and also Com_stmt_prepare.
10
Q
Compression
A
Whether the client connection uses compression in the client/server protocol.
11
Q
Connection_errors_accept
A
The number of errors that occurred during calls toaccept()on the listening port.
12
Q
Connection_errors_internal
A
The number of connections refused due to internal errors in the server such as failure to start a new thread or an out-of-memory condition.
13
Q
Connection_errors_max_connections
A
The number of connections refused because the servermax_connectionslimit was reached.
14
Q
Connection_errors_peer_addr
A
The number of errors that occurred while searching for connecting client IP addresses.
15
Q
Connection_errors_select
A
The number of errors that occurred during calls toselect()orpoll()on the listening port. (Failure of this operation does not necessarily means a client connection was rejected.)
16
Q
Connection_errors_tcpwrap
A
The number of connections refused by thelibwraplibrary.
17
Q
Connection_errors_xxx
A
These variables provide information about errors that occur during the client connection process. They are global only and represent error counts aggregated across connections from all hosts. These variables track errors not accounted for by the host cache (seeSection8.11.5.2 “DNS Lookup Optimization and the Host Cache”) such as errors that are not associated with TCP connections occur very early in the connection process (even before an IP address is known) or are not specific to any particular IP address (such as out-of-memory conditions). These variables were added in MySQL 5.6.5.
18
Q
Connections
A
The number of connection attempts (successful or not) to the MySQL server.
19
Q
Created_tmp_disk_tables
A
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 and max_heap_table_size values. If Created_tmp_disk_tables is large you may want to increase the tmp_table_size or max_heap_table_size 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 and Created_tmp_tables variables.
20
Q
Created_tmp_files
A
How many temporary filesmysqldhas created.
21
Q
Created_tmp_tables
A
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 and Created_tmp_tables variables.
See also Section 8.4.4 “How MySQL Uses Internal Temporary Tables”.
Each invocation of the SHOW STATUS statement uses an internal temporary table and increments the global Created_tmp_tables value.
22
Q
Delayed_errors
A
deprecated as of 5.6.7
23
Q
Delayed_insert_threads
A
deprecated as of 5.6.7
24
Q
Delayed_writes
A
deprecated as of 5.6.7
25
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 a COM_REFRESH packet. This is in contrast to Com_flush which indicates how many FLUSH statements have been executed whether FLUSH TABLES FLUSH LOGS and so forth.
26
Handler_commit
The number of internal COMMIT statements.
27
Handler_delete
The number of times that rows have been deleted from tables.
28
Handler_external_lock
The server increments this variable for each call to its external_lock() function which generally occurs at the beginning and end of access to a table instance. There might be differences among storage engines. This variable can be used for example to discover for a statement that accesses a partitioned table how many partitions were pruned before locking occurred: Check how much the counter increased for the statement subtract 2 (2 calls for the table itself) then divide by 2 to get the number of partitions locked. This variable was added in MySQL 5.6.2.
29
Handler_mrr_init
The number of times the server uses a storage engines own Multi-Range Read implementation for table access. This variable was added in MySQL 5.6.1.
30
Handler_prepare
A counter for the prepare phase of two-phase commit operations.
31
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 that col1 is indexed.
32
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.
33
Handler_read_last
The number of requests to read the last key in an index. With ORDER BY the server will issue a first-key request followed by several next-key requests whereas with With ORDER BY DESC the server will issue a last-key request followed by several previous-key requests. This variable was added in MySQL 5.6.1.
34
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.
35
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.
36
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.
37
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.
38
Handler_rollback
The number of requests for a storage engine to perform a rollback operation.
39
Handler_savepoint
The number of requests for a storage engine to place a savepoint.
40
Handler_savepoint_rollback
The number of requests for a storage engine to roll back to a savepoint.
41
Handler_update
The number of requests to update a row in a table.
42
Handler_write
The number of requests to insert a row in a table.
43
Innodb_available_undo_logs
The total number of available InnoDB undo logs. Supplements the innodb_undo_logs system variable which reports the number of active undo logs.
44
Innodb_buffer_pool_bytes_data
The total number of bytes in the InnoDB buffer pool containing data. The number includes both dirty and clean pages. For more accurate memory usage calculations than with Innodb_buffer_pool_pages_data when compressed tables cause the buffer pool to hold pages of different sizes.
45
Innodb_buffer_pool_bytes_dirty
The total current number of bytes held in dirty pages in the InnoDB buffer pool. For more accurate memory usage calculations than with Innodb_buffer_pool_pages_dirty when compressed tables cause the buffer pool to hold pages of different sizes.
46
Innodb_buffer_pool_dump_status
The progress of an operation to record the pages held in the InnoDB buffer pool triggered by the setting ofinnodb_buffer_pool_dump_at_shutdown or innodb_buffer_pool_dump_now.
47
Innodb_buffer_pool_load_status
The progress of an operation to warm up the InnoDB buffer pool by reading in a set of pages corresponding to an earlier point in time triggered by the setting of innodb_buffer_pool_load_at_startup orinnodb_buffer_pool_load_now. If the operation introduces too much overhead you can cancel it by settinginnodb_buffer_pool_load_abort.
48
Innodb_buffer_pool_pages_data
The number of pages in the InnoDB buffer pool containing data. The number includes both dirty and clean pages.
49
Innodb_buffer_pool_pages_dirty
The current number of dirty pages in the InnoDB buffer pool.
50
Innodb_buffer_pool_pages_flushed
The number of requests to flush pages from the InnoDB buffer pool.
51
Innodb_buffer_pool_pages_free
The number of free pages in the InnoDB buffer pool.
52
Innodb_buffer_pool_pages_latched
The number of latched pages in the InnoDB buffer pool. These are pages currently being read or written or that cannot beflushed or removed for some other reason. Calculation of this variable is expensive so it is available only when theUNIV_DEBUG system is defined at server build time.
53
Innodb_buffer_pool_pages_misc
The number of pages in the InnoDB buffer pool 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 asInnodb_buffer_pool_pages_total – Innodb_buffer_pool_pages_free –Innodb_buffer_pool_pages_data.
54
Innodb_buffer_pool_pages_total
The total size of the InnoDB buffer pool in pages.
55
Innodb_buffer_pool_read_ahead
The number of pages read into the InnoDB buffer pool by the read-ahead background thread.
56
Innodb_buffer_pool_read_ahead_evicted
The number of pages read into the InnoDB buffer pool by the read-ahead background thread that were subsequentlyevicted without having been accessed by queries.
57
Innodb_buffer_pool_read_requests
The number of logical read requests made to the InnoDB buffer pool. These requests could be serviced by returning data that was already in memory or by reading the data from disk into memory first.
58
Innodb_buffer_pool_reads
The number of logical reads that InnoDB could not satisfy from the buffer pool and had to read directly from disk.
59
Innodb_buffer_pool_wait_free
Normally writes to the InnoDB buffer pool happen in the background. When InnoDB needs to read or create a page and no clean pages are available InnoDB flushes some dirty pages first and waits for that operation to finish. This counter counts instances of these waits. If innodb_buffer_pool_size has been set properly this value should be small.
60
Innodb_buffer_pool_write_requests
The number of writes done to the InnoDB buffer pool.
61
Innodb_data_fsyncs
The number of fsync() operations so far. The frequency of fsync() calls is influenced by the setting of theinnodb_flush_method configuration option.
62
Innodb_data_pending_fsyncs
The current number of pending fsync() operations. The frequency of fsync() calls is influenced by the setting of theinnodb_flush_method configuration option.
63
Innodb_data_pending_reads
The current number of pending reads.
64
Innodb_data_pending_writes
The current number of pending writes.
65
Innodb_data_read
The amount of data read since the server was started.
66
Innodb_data_reads
The total number of data reads.
67
Innodb_data_writes
The total number of data writes.
68
Innodb_data_written
The amount of data written so far in bytes.
69
Innodb_dblwr_pages_written
The number of pages that have been written to the doublewrite buffer. See Section 14.2.10.1 “InnoDB Disk I/O”.
70
Innodb_dblwr_writes
The number of doublewrite operations that have been performed. See Section 14.2.10.1 “InnoDB Disk I/O”.
71
Innodb_have_atomic_builtins
Indicates whether the server was built with atomic instructions.
72
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.
73
Innodb_log_write_requests
The number of write requests for the InnoDB redo log.
74
Innodb_log_writes
The number of physical writes to the InnoDB redo log file.
75
Innodb_num_open_files
The number of files InnoDB currently holds open.
76
Innodb_os_log_fsyncs
The number of fsync() writes done to the InnoDB redo log files.
77
Innodb_os_log_pending_fsyncs
The number of pending fsync() operations for the InnoDB redo log files.
78
Innodb_os_log_pending_writes
The number of pending writes to the InnoDB redo log files.
79
Innodb_os_log_written
The number of bytes written to the InnoDB redo log files.
80
Innodb_page_size
The compiled-in InnoDB page size (default 16KB). Many values are counted in pages; the page size enables them to be easily converted to bytes.
81
Innodb_pages_created
The number of pages created by operations on InnoDB tables.
82
Innodb_pages_read
The number of pages read by operations on InnoDB tables.
83
Innodb_pages_written
The number of pages written by operations on InnoDB tables.
84
Innodb_row_lock_current_waits
The number of row locks currently being waited for by operations on InnoDB tables.
85
Innodb_row_lock_time
The total time spent in acquiring row locks for InnoDB tables in milliseconds.
86
Innodb_row_lock_time_avg
The average time to acquire a row lock for InnoDB tables in milliseconds.
87
Innodb_row_lock_time_max
The maximum time to acquire a row lock for InnoDB tables in milliseconds.
88
Innodb_row_lock_waits
The number of times operations on InnoDB tables had to wait for a row lock.
89
Innodb_rows_deleted
The number of rows deleted from InnoDB tables.
90
Innodb_rows_inserted
The number of rows inserted into InnoDB tables.
91
Innodb_rows_read
The number of rows read from InnoDB tables.
92
Innodb_rows_updated
The number of rows updated in InnoDB tables.
93
Innodb_truncated_status_writes
The number of times output from the SHOW ENGINE INNODB STATUS statement has been truncated.
94
Key_blocks_not_flushed
The number of key blocks in the MyISAM key cache that have changed but have not yet been flushed to disk.
95
Key_blocks_unused
The number of unused blocks in the MyISAM 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”.
96
Key_blocks_used
The number of used blocks in the MyISAM 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.
97
Key_read_requests
The number of requests to read a key block from the MyISAM key cache.
98
Key_reads
The number of physical reads of a key block from disk into the MyISAM key cache. 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.
99
Key_write_requests
The number of requests to write a key block to the MyISAM key cache.
100
Key_writes
The number of physical writes of a key block from the MyISAM key cache to disk.
101
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. The default value is 0. Last_query_cost has session scope.
The Last_query_cost value can be computed accurately only for simple “flat” queries not complex queries such as those with subqueries or UNION. For the latter the value is set to 0.
102
Last_query_partial_plans
The number of iterations the query optimizer made in execution plan construction for the previous query.Last_query_cost has session scope. This variable was added in MySQL 5.6.5.
103
Max_used_connections
The maximum number of connections that have been in use simultaneously since the server started.
104
Not_flushed_delayed_rows
deprecated as of 5.6.7
105
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.
106
Open_streams
The number of streams that are open (used mainly for logging).
107
Open_table_definitions
The number of cached .frm files.
108
Open_tables
The number of tables that are open.
109
Opened_files
The number of files that have been opened with my_open() (a mysys library function). Parts of the server that open files without using this function do not increment the count.
110
Opened_table_definitions
The number of .frm files that have been cached.
111
Opened_tables
The number of tables that have been opened. If Opened_tables is big your table_open_cache value is probably too small.
112
Prepared_stmt_count
The current number of prepared statements. (The maximum number of statements is given by themax_prepared_stmt_count system variable.)
113
Qcache_free_blocks
The number of free memory blocks in the query cache.
114
Qcache_free_memory
The amount of free memory for the query cache.
115
Qcache_hits
The number of query cache hits.
116
Qcache_inserts
The number of queries added to the query cache.
117
Qcache_lowmem_prunes
The number of queries that were deleted from the query cache because of low memory.
118
Qcache_not_cached
The number of noncached queries (not cacheable or not cached due to the query_cache_type setting).
119
Qcache_queries_in_cache
The number of queries registered in the query cache.
120
Qcache_total_blocks
The total number of blocks in the query cache.
121
Queries
The number of statements executed by the server. This variable includes statements executed within stored programs unlike the Questions variable. It does not count COM_PING or COM_STATISTICS commands.
122
Questions
The number of statements executed by the server. This includes only statements sent to the server by clients and not statements executed within stored programs unlike the Queries variable. This variable does not count COM_PINGCOM_STATISTICS COM_STMT_PREPARE COM_STMT_CLOSE or COM_STMT_RESET commands.
123
Rpl_semi_sync_master_clients
The number of semisynchronous slaves.
This variable is available only if the master-side semisynchronous replication plugin is installed.
124
Rpl_semi_sync_master_net_avg_wait_time
The average time in microseconds the master waited for a slave reply.
This variable is available only if the master-side semisynchronous replication plugin is installed.
125
Rpl_semi_sync_master_net_wait_time
The total time in microseconds the master waited for slave replies.
This variable is available only if the master-side semisynchronous replication plugin is installed.
126
Rpl_semi_sync_master_net_waits
The total number of times the master waited for slave replies.
This variable is available only if the master-side semisynchronous replication plugin is installed.
127
Rpl_semi_sync_master_no_times
The number of times the master turned off semisynchronous replication.
This variable is available only if the master-side semisynchronous replication plugin is installed.
128
Rpl_semi_sync_master_no_tx
The number of commits that were not acknowledged successfully by a slave.
This variable is available only if the master-side semisynchronous replication plugin is installed.
129
Rpl_semi_sync_master_status
Whether semisynchronous replication currently is operational on the master. The value is ON if the plugin has been enabled and a commit acknowledgment has occurred. It is OFF if the plugin is not enabled or the master has fallen back to asynchronous replication due to commit acknowledgment timeout.
This variable is available only if the master-side semisynchronous replication plugin is installed.
130
Rpl_semi_sync_master_timefunc_failures
The number of times the master failed when calling time functions such as gettimeofday().
This variable is available only if the master-side semisynchronous replication plugin is installed.
131
Rpl_semi_sync_master_tx_avg_wait_time
The average time in microseconds the master waited for each transaction.
This variable is available only if the master-side semisynchronous replication plugin is installed.
132
Rpl_semi_sync_master_tx_wait_time
The total time in microseconds the master waited for transactions.
This variable is available only if the master-side semisynchronous replication plugin is installed.
133
Rpl_semi_sync_master_tx_waits
The total number of times the master waited for transactions.
This variable is available only if the master-side semisynchronous replication plugin is installed.
134
Rpl_semi_sync_master_wait_pos_backtraverse
The total number of times the master waited for an event with binary coordinates lower than events waited for previously. This can occur when the order in which transactions start waiting for a reply is different from the order in which their binary log events are written.
This variable is available only if the master-side semisynchronous replication plugin is installed.
135
Rpl_semi_sync_master_wait_sessions
The number of sessions currently waiting for slave replies.
This variable is available only if the master-side semisynchronous replication plugin is installed.
136
Rpl_semi_sync_master_yes_tx
The number of commits that were acknowledged successfully by a slave.
This variable is available only if the master-side semisynchronous replication plugin is installed.
137
Rpl_semi_sync_slave_status
Whether semisynchronous replication currently is operational on the slave. This is ON if the plugin has been enabled and the slave I/O thread is running OFF otherwise.
This variable is available only if the slave-side semisynchronous replication plugin is installed.
138
Rsa_public_key
The RSA public key value used by the sha256_password authentication plugin. The value is nonempty only if the server successfully initializes the private and public keys in the files named by the sha256_password_private_key_path and sha256_password_public_key_path system variables. The value of Rsa_public_key comes from the latter file.
For information about sha256_password see Section 6.3.8.4 “The SHA-256 Authentication Plugin”.
This variable is available only if MySQL was built using OpenSSL. It was added in MySQL 5.6.6.
139
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.
140
Select_full_range_join
The number of joins that used a range search on a reference table.
141
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.
142
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.
143
Select_scan
The number of joins that did a full scan of the first table.
144
Slave_heartbeat_period
Shows the replication heartbeat interval (in seconds) on a replication slave.
145
Slave_last_heartbeat
Shows when the most recent heartbeat signal was received by a replication slave as a TIMESTAMP value.
146
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.22 “Replication and Temporary Tables”.
147
Slave_received_heartbeats
This counter increments with each replication heartbeat received by a replication slave since the last time that the slave was restarted or reset or a CHANGE MASTER TO statement was issued.
148
Slave_retried_transactions
The total number of times since startup that the replication slave SQL thread has retried transactions.
149
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 is OFF.
150
Slow_launch_threads
The number of threads that have taken more than slow_launch_time seconds to create.
151
Slow_queries
The number of queries that have taken more than long_query_time seconds. This counter increments regardless of whether the slow query log is enabled. For information about that log see Section 5.2.5 “The Slow Query Log”.
152
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.
153
Sort_range
The number of sorts that were done using ranges.
154
Sort_rows
The number of sorted rows.
155
Sort_scan
The number of sorts that were done by scanning the table.
156
Ssl_accept_renegotiates
The number of negotiates needed to establish the connection.
157
Ssl_accepts
The number of accepted SSL connections.
158
Ssl_callback_cache_hits
The number of callback cache hits.
159
Ssl_cipher
The current SSL cipher (empty for non-SSL connections).
160
Ssl_cipher_list
The list of possible SSL ciphers.
161
Ssl_client_connects
The number of SSL connection attempts to an SSL-enabled master.
162
Ssl_connect_renegotiates
The number of negotiates needed to establish the connection to an SSL-enabled master.
163
Ssl_ctx_verify_depth
The SSL context verification depth (how many certificates in the chain are tested).
164
Ssl_ctx_verify_mode
The SSL context verification mode.
165
Ssl_default_timeout
The default SSL timeout.
166
Ssl_finished_accepts
The number of successful SSL connections to the server.
167
Ssl_finished_connects
The number of successful slave connections to an SSL-enabled master.
168
Ssl_server_not_after
The last date for which the SSL certificate is valid. This variable was added in MySQL 5.6.3.
169
Ssl_server_not_before
The first date for which the SSL certificate is valid. This variable was added in MySQL 5.6.3.
170
Ssl_session_cache_hits
The number of SSL session cache hits.
171
Ssl_session_cache_misses
The number of SSL session cache misses.
172
Ssl_session_cache_mode
The SSL session cache mode.
173
Ssl_session_cache_overflows
The number of SSL session cache overflows.
174
Ssl_session_cache_size
The SSL session cache size.
175
Ssl_session_cache_timeouts
The number of SSL session cache timeouts.
176
Ssl_sessions_reused
How many SSL connections were reused from the cache.
177
Ssl_used_session_cache_entries
How many SSL session cache entries were used.
178
Ssl_verify_depth
The verification depth for replication SSL connections.
179
Ssl_verify_mode
The verification mode for replication SSL connections.
180
Ssl_version
The SSL protocol version of the connection.
181
Table_locks_immediate
The number of times that a request for a table lock could be granted immediately.
182
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.
183
Table_open_cache_hits
The number of hits for open tables cache lookups. This variable was added in MySQL 5.6.6.
184
Table_open_cache_misses
The number of misses for open tables cache lookups. This variable was added in MySQL 5.6.6.
185
Table_open_cache_overflows
The number of overflows for the open tables cache. This is the number of times after a table is opened or closed a cache instance has an unused entry and the size of the instance is larger than table_open_cache /table_open_cache_instances. This variable was added in MySQL 5.6.6.
186
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 and Tc_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.)
187
Tc_log_page_size
The page size used for the memory-mapped implementation of the XA recovery log. The default value is determined usinggetpagesize(). Currently this variable is unused for the same reasons as described for Tc_log_max_pages_used.
188
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.)
189
Threads_cached
The number of threads in the thread cache.
190
Threads_connected
The number of currently open connections.
191
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 as Threads_created/Connections.
192
Threads_running
The number of threads that are not sleeping.
193
Uptime
The number of seconds that the server has been up.
194
Uptime_since_flush_status
The number of seconds since the most recent FLUSH STATUS statement.
195
Performance_schema_xxx
Performance Schema status variables are listed in Section 21.13 “Performance Schema Status Variables”. These variables provide information about instrumentation that could not be loaded or created due to memory constraints.
