Aborted clients | 18 18 | The number of connections that were aborted because the client died without closing the connection properly. |
---|
Aborted connects | 00 | The number of failed attempts to connect to the MySQL server. |
---|
Binlog cache disk use | 00 | 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 | 00 | The number of transactions that used the temporary binary log cache. |
---|
Binlog stmt cache disk use | 00 | |
---|
Binlog stmt cache use | 00 | |
---|
Bytes received | 405 M404997698 | |
---|
Bytes sent | 11.6 G11572816616 | |
---|
Com admin commands | 1 1 | |
---|
Com assign to keycache | 00 | |
---|
Com alter db | 00 | |
---|
Com alter db upgrade | 00 | |
---|
Com alter event | 00 | |
---|
Com alter function | 00 | |
---|
Com alter procedure | 00 | |
---|
Com alter server | 00 | |
---|
Com alter table | 00 | |
---|
Com alter tablespace | 00 | |
---|
Com analyze | 00 | |
---|
Com begin | 00 | |
---|
Com binlog | 00 | |
---|
Com call procedure | 00 | |
---|
Com change db | 230 k230034 | |
---|
Com change master | 00 | |
---|
Com check | 00 | |
---|
Com checksum | 00 | |
---|
Com commit | 00 | |
---|
Com create db | 00 | |
---|
Com create event | 00 | |
---|
Com create function | 00 | |
---|
Com create index | 00 | |
---|
Com create procedure | 00 | |
---|
Com create server | 00 | |
---|
Com create table | 00 | |
---|
Com create trigger | 00 | |
---|
Com create udf | 00 | |
---|
Com create user | 00 | |
---|
Com create view | 00 | |
---|
Com delete | 24.1 k24079 | |
---|
Com delete multi | 00 | |
---|
Com do | 00 | |
---|
Com drop db | 00 | |
---|
Com drop event | 00 | |
---|
Com drop function | 00 | |
---|
Com drop index | 00 | |
---|
Com drop procedure | 00 | |
---|
Com drop server | 00 | |
---|
Com drop table | 00 | |
---|
Com drop trigger | 00 | |
---|
Com drop user | 00 | |
---|
Com drop view | 00 | |
---|
Com empty query | 00 | |
---|
Com flush | 00 | |
---|
Com grant | 00 | |
---|
Com ha close | 00 | |
---|
Com ha open | 00 | |
---|
Com ha read | 00 | |
---|
Com help | 00 | |
---|
Com insert | 4.9 k4923 | |
---|
Com insert select | 00 | |
---|
Com install plugin | 00 | |
---|
Com kill | 00 | |
---|
Com load | 00 | |
---|
Com lock tables | 00 | |
---|
Com optimize | 00 | |
---|
Com preload keys | 00 | |
---|
Com purge | 00 | |
---|
Com purge before date | 00 | |
---|
Com release savepoint | 00 | |
---|
Com rename table | 00 | |
---|
Com rename user | 00 | |
---|
Com repair | 00 | |
---|
Com replace | 22.5 k22514 | |
---|
Com replace select | 00 | |
---|
Com reset | 00 | |
---|
Com resignal | 00 | |
---|
Com revoke | 00 | |
---|
Com revoke all | 00 | |
---|
Com rollback | 00 | |
---|
Com rollback to savepoint | 00 | |
---|
Com savepoint | 00 | |
---|
Com select | 3.2 M3201901 | |
---|
Com set option | 390.9 k390887 | |
---|
Com signal | 00 | |
---|
Com show authors | 00 | |
---|
Com show binlog events | 00 | |
---|
Com show binlogs | 362 k362043 | |
---|
Com show charsets | 00 | |
---|
Com show collations | 00 | |
---|
Com show contributors | 00 | |
---|
Com show create db | 00 | |
---|
Com show create event | 00 | |
---|
Com show create func | 00 | |
---|
Com show create proc | 00 | |
---|
Com show create table | 4.7 k4714 | |
---|
Com show create trigger | 00 | |
---|
Com show databases | 357.4 k357407 | |
---|
Com show engine logs | 00 | |
---|
Com show engine mutex | 00 | |
---|
Com show engine status | 00 | |
---|
Com show events | 125 125 | |
---|
Com show errors | 00 | |
---|
Com show fields | 173 k172997 | |
---|
Com show function status | 125 125 | |
---|
Com show grants | 20.9 k20947 | |
---|
Com show keys | 80.5 k80477 | |
---|
Com show master status | 35.2 k35206 | |
---|
Com show open tables | 00 | |
---|
Com show plugins | 00 | |
---|
Com show privileges | 00 | |
---|
Com show procedure status | 125 125 | |
---|
Com show processlist | 4.6 k4610 | |
---|
Com show profile | 00 | |
---|
Com show profiles | 00 | |
---|
Com show relaylog events | 00 | |
---|
Com show slave hosts | 00 | |
---|
Com show slave status | 35.2 k35206 | |
---|
Com show status | 6.9 k6938 | |
---|
Com show storage engines | 6.3 k6251 | |
---|
Com show table status | 255 k254992 | |
---|
Com show tables | 168.7 k168656 | |
---|
Com show triggers | 763 763 | |
---|
Com show variables | 92.9 k92942 | |
---|
Com show warnings | 00 | |
---|
Com slave start | 00 | |
---|
Com slave stop | 00 | |
---|
Com stmt close | 00 | |
---|
Com stmt execute | 00 | |
---|
Com stmt fetch | 00 | |
---|
Com stmt prepare | 00 | |
---|
Com stmt reprepare | 00 | |
---|
Com stmt reset | 00 | |
---|
Com stmt send long data | 00 | |
---|
Com truncate | 00 | |
---|
Com uninstall plugin | 00 | |
---|
Com unlock tables | 00 | |
---|
Com update | 238.6 k238632 | |
---|
Com update multi | 00 | |
---|
Com xa commit | 00 | |
---|
Com xa end | 00 | |
---|
Com xa prepare | 00 | |
---|
Com xa recover | 00 | |
---|
Com xa rollback | 00 | |
---|
Com xa start | 00 | |
---|
Compression | OFFOFF | |
---|
Connections | 209 k208997 | The number of connection attempts (successful or not) to the MySQL server. |
---|
Created tmp disk tables | 755.7 k755717 | The 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 files | 00 | How many temporary files mysqld has created. |
---|
Created tmp tables | 4.6 M4617909 | The number of in-memory temporary tables created automatically by the server while executing statements. |
---|
Delayed errors | 00 | The number of rows written with INSERT DELAYED for which some error occurred (probably duplicate key). |
---|
Delayed insert threads | 00 | The number of INSERT DELAYED handler threads in use. Every different table on which one uses INSERT DELAYED gets its own thread. |
---|
Delayed writes | 00 | The number of INSERT DELAYED rows written. |
---|
Flush commands | 1 1 | The number of executed FLUSH statements. |
---|
Handler commit | 00 | The number of internal COMMIT statements. |
---|
Handler delete | 530 530 | The number of times a row was deleted from a table. |
---|
Handler discover | 00 | The 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 prepare | 00 | |
---|
Handler read first | 166.2 k166161 | The 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 key | 3.2 M3213082 | The 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 last | 13.8 k13757 | |
---|
Handler read next | 13.4 M13376843 | The 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 prev | 607.9 k607880 | 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 | 16.5 M16468384 | The 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 next | 118.7 M118724956 | The 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 rollback | 00 | The number of internal ROLLBACK statements. |
---|
Handler savepoint | 00 | |
---|
Handler savepoint rollback | 00 | |
---|
Handler update | 871.6 k871606 | The number of requests to update a row in a table. |
---|
Handler write | 62.7 M62677775 | The number of requests to insert a row in a table. |
---|
Key blocks not flushed | 00 | The 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 unused | 14.3 k14337 | 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. |
---|
Key blocks used | 1.6 k1627 | 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 | 21.4 M21405863 | The number of requests to read a key block from the cache. |
---|
Key reads | 254.9 k254893 | The 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 requests | 420.4 k420417 | The number of requests to write a key block to the cache. |
---|
Key writes | 164.9 k164850 | The number of physical writes of a key block to disk. |
---|
Last query cost | 00.000000 | The 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. |
---|
Max used connections | 18 18 | The maximum number of connections that have been in use simultaneously since the server started. |
---|
Not flushed delayed rows | 00 | The number of rows waiting to be written in INSERT DELAYED queues. |
---|
Open files | 94 94 | The number of files that are open. |
---|
Open streams | 00 | The number of streams that are open (used mainly for logging). |
---|
Open table definitions | 168 168 | |
---|
Open tables | 64 64 | The number of tables that are open. |
---|
Opened files | 11.7 M11671848 | |
---|
Opened table definitions | 147 147 | |
---|
Opened tables | 6.8 M6800587 | The number of tables that have been opened. If opened tables is big, your table cache value is probably too small. |
---|
Performance schema cond classes lost | 00 | |
---|
Performance schema cond instances lost | 00 | |
---|
Performance schema file classes lost | 00 | |
---|
Performance schema file handles lost | 00 | |
---|
Performance schema file instances lost | 00 | |
---|
Performance schema locker lost | 00 | |
---|
Performance schema mutex classes lost | 00 | |
---|
Performance schema mutex instances lost | 00 | |
---|
Performance schema rwlock classes lost | 00 | |
---|
Performance schema rwlock instances lost | 00 | |
---|
Performance schema table handles lost | 00 | |
---|
Performance schema table instances lost | 00 | |
---|
Performance schema thread classes lost | 00 | |
---|
Performance schema thread instances lost | 00 | |
---|
Prepared stmt count | 00 | |
---|
Qcache free blocks | 00 | The number of free memory blocks in query cache. High numbers can indicate fragmentation issues, which may be solved by issuing a FLUSH QUERY CACHE statement. |
---|
Qcache free memory | 00 | The amount of free memory for query cache. |
---|
Qcache hits | 00 | The number of cache hits. |
---|
Qcache inserts | 00 | The number of queries added to the cache. |
---|
Qcache lowmem prunes | 00 | The 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 cached | 00 | The number of non-cached queries (not cachable, or not cached due to the query_cache_type setting). |
---|
Qcache queries in cache | 00 | The number of queries registered in the cache. |
---|
Qcache total blocks | 00 | The total number of blocks in the query cache. |
---|
Queries | 5.9 M5926506 | |
---|
Questions | 5.9 M5926506 | |
---|
Rpl status | AUTH_MASTERAUTH_MASTER | The status of failsafe replication (not yet implemented). |
---|
Select full join | 223 223 | The 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 join | 8 8 | The number of joins that used a range search on a reference table. |
---|
Select range | 120.3 k120305 | The number of joins that used ranges on the first table. (It's normally not critical even if this is big.) |
---|
Select range check | 00 | 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 | 2.1 M2053065 | The number of joins that did a full scan of the first table. |
---|
Slave heartbeat period | 00.000 | |
---|
Slave open temp tables | 00 | The number of temporary tables currently open by the slave SQL thread. |
---|
Slave received heartbeats | 00 | |
---|
Slave retried transactions | 00 | Total (since startup) number of times the replication slave SQL thread has retried transactions. |
---|
Slave running | OFFOFF | This is ON if this server is a slave that is connected to a master. |
---|
Slow launch threads | 00 | The number of threads that have taken more than slow_launch_time seconds to create. |
---|
Slow queries | 126 126 | The number of queries that have taken more than long_query_time seconds. |
---|
Sort merge passes | 00 | The 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 range | 194.1 k194058 | The number of sorts that were done with ranges. |
---|
Sort rows | 16.7 M16651853 | The number of sorted rows. |
---|
Sort scan | 330.3 k330294 | The number of sorts that were done by scanning the table. |
---|
Ssl accept renegotiates | 00 | |
---|
Ssl accepts | 00 | |
---|
Ssl callback cache hits | 00 | |
---|
Ssl cipher | | |
---|
Ssl cipher list | | |
---|
Ssl client connects | 00 | |
---|
Ssl connect renegotiates | 00 | |
---|
Ssl ctx verify depth | 00 | |
---|
Ssl ctx verify mode | 00 | |
---|
Ssl default timeout | 00 | |
---|
Ssl finished accepts | 00 | |
---|
Ssl finished connects | 00 | |
---|
Ssl session cache hits | 00 | |
---|
Ssl session cache misses | 00 | |
---|
Ssl session cache mode | NONENONE | |
---|
Ssl session cache overflows | 00 | |
---|
Ssl session cache size | 00 | |
---|
Ssl session cache timeouts | 00 | |
---|
Ssl sessions reused | 00 | |
---|
Ssl used session cache entries | 00 | |
---|
Ssl verify depth | 00 | |
---|
Ssl verify mode | 00 | |
---|
Ssl version | | |
---|
Table locks immediate | 2.8 M2760906 | The number of times that a table lock was acquired immediately. |
---|
Table locks waited | 00 | The 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. |
---|
Tc log max pages used | 00 | |
---|
Tc log page size | 00 | |
---|
Tc log page waits | 00 | |
---|
Threads cached | 00 | The 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 connected | 2 2 | The number of currently open connections. |
---|
Threads created | 209 k208996 | The 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 running | 1 1 | The number of threads that are not sleeping. |
---|
Uptime | 42 days, 12 hours, 24 minutes and 0 seconds3673440 | |
---|
Uptime since flush status | 42 days, 12 hours, 24 minutes and 0 seconds3673440 | |
---|
Key buffer fraction % | 12.49 %12.493896484375 | Percentage of used key cache (calculated value) |
---|
Key write ratio % | 39.21 %39.211069010054 | Percentage of physical writes compared to write requests (calculated value) |
---|
Key read ratio % | 1.19 %1.190762549494 | Key cache miss calculated as rate of physical reads compared to read requests (calculated value) |
---|
Threads cache hitrate % | <0.01 %0.00047847576759352 | Thread cache hit rate (calculated value) |
---|