Press Ctrl+Enter to execute queryPress Enter to execute query
- There are no favorite tables.
Drop files here
Console| Variable | Value | Description |
|---|---|---|
| Aborted clients | 0 | The number of connections that were aborted because the client died without closing the connection properly. |
| Aborted connects | 7 | The number of failed attempts to connect to the MySQL server. |
| Access denied errors | 0 | |
| Acl column grants | 0 | |
| Acl database grants | 4 | |
| Acl function grants | 0 | |
| Acl procedure grants | 0 | |
| Acl proxy users | 1 | |
| Acl role grants | 0 | |
| Acl roles | 0 | |
| Acl table grants | 0 | |
| Acl users | 9 | |
| Aria pagecache blocks not flushed | 0 | |
| Aria pagecache blocks unused | 15.7 k | |
| Aria pagecache blocks used | 672 | |
| Aria pagecache read requests | 4.8 M | |
| Aria pagecache reads | 113.9 k | |
| Aria pagecache write requests | 282.2 k | |
| Aria pagecache writes | 0 | |
| Aria transaction log syncs | 0 | |
| Binlog commits | 0 | |
| Binlog group commits | 0 | |
| Binlog group commit trigger count | 0 | |
| Binlog group commit trigger lock wait | 0 | |
| Binlog group commit trigger timeout | 0 | |
| Binlog snapshot file | ||
| Binlog snapshot position | 0 | |
| Binlog bytes written | 0 | |
| Binlog cache disk use | 0 | 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 | 0 | The number of transactions that used the temporary binary log cache. |
| Binlog stmt cache disk use | 0 | |
| Binlog stmt cache use | 0 | |
| Busy time | 0 | |
| Bytes received | 608.3 M | |
| Bytes sent | 2.5 G | |
| Com admin commands | 0 | |
| Com alter db | 0 | |
| Com alter db upgrade | 0 | |
| Com alter event | 0 | |
| Com alter function | 0 | |
| Com alter procedure | 0 | |
| Com alter server | 0 | |
| Com alter table | 0 | |
| Com alter tablespace | 0 | |
| Com analyze | 0 | |
| Com assign to keycache | 0 | |
| Com begin | 0 | |
| Com binlog | 0 | |
| Com call procedure | 0 | |
| Com change db | 23.7 k | |
| Com change master | 0 | |
| Com check | 0 | |
| Com checksum | 0 | |
| Com commit | 0 | |
| Com compound sql | 0 | |
| Com create db | 0 | |
| Com create event | 0 | |
| Com create function | 0 | |
| Com create index | 0 | |
| Com create procedure | 0 | |
| Com create role | 0 | |
| Com create server | 0 | |
| Com create table | 0 | |
| Com create temporary table | 0 | |
| Com create trigger | 0 | |
| Com create udf | 0 | |
| Com create user | 0 | |
| Com create view | 0 | |
| Com delete | 17.9 k | |
| Com delete multi | 0 | |
| Com do | 0 | |
| Com drop db | 0 | |
| Com drop event | 0 | |
| Com drop function | 0 | |
| Com drop index | 0 | |
| Com drop procedure | 0 | |
| Com drop role | 0 | |
| Com drop server | 0 | |
| Com drop table | 0 | |
| Com drop temporary table | 0 | |
| Com drop trigger | 0 | |
| Com drop user | 0 | |
| Com drop view | 0 | |
| Com empty query | 0 | |
| Com flush | 12.1 k | |
| Com get diagnostics | 0 | |
| Com grant | 0 | |
| Com grant role | 0 | |
| Com ha close | 0 | |
| Com ha open | 0 | |
| Com ha read | 0 | |
| Com help | 0 | |
| Com insert | 17.9 k | |
| Com insert select | 0 | |
| Com install plugin | 0 | |
| Com kill | 0 | |
| Com load | 0 | |
| Com lock tables | 0 | |
| Com optimize | 0 | |
| Com preload keys | 0 | |
| Com purge | 0 | |
| Com purge before date | 0 | |
| Com release savepoint | 0 | |
| Com rename table | 0 | |
| Com rename user | 0 | |
| Com repair | 0 | |
| Com replace | 2.4 k | |
| Com replace select | 0 | |
| Com reset | 0 | |
| Com resignal | 0 | |
| Com revoke | 0 | |
| Com revoke all | 0 | |
| Com revoke role | 0 | |
| Com rollback | 0 | |
| Com rollback to savepoint | 0 | |
| Com savepoint | 0 | |
| Com select | 1.6 M | |
| Com set option | 24.2 k | |
| Com show authors | 0 | |
| Com show binlog events | 0 | |
| Com show binlogs | 1.5 k | |
| Com show charsets | 0 | |
| Com show collations | 0 | |
| Com show contributors | 0 | |
| Com show create db | 0 | |
| Com show create event | 0 | |
| Com show create func | 0 | |
| Com show create proc | 188 | |
| Com show create table | 43.3 k | |
| Com show create trigger | 0 | |
| Com show databases | 0 | |
| Com show engine logs | 0 | |
| Com show engine mutex | 0 | |
| Com show engine status | 0 | |
| Com show errors | 0 | |
| Com show events | 0 | |
| Com show explain | 0 | |
| Com show fields | 109.7 k | |
| Com show function status | 0 | |
| Com show generic | 0 | |
| Com show grants | 4.5 k | |
| Com show keys | 104.5 k | |
| Com show master status | 3.3 k | |
| Com show open tables | 0 | |
| Com show plugins | 121 | |
| Com show privileges | 0 | |
| Com show procedure status | 0 | |
| Com show processlist | 4 | |
| Com show profile | 0 | |
| Com show profiles | 0 | |
| Com show relaylog events | 0 | |
| Com show slave hosts | 0 | |
| Com show slave status | 3.3 k | |
| Com show status | 88 | |
| Com show storage engines | 148 | |
| Com show table status | 2.4 k | |
| Com show tables | 30 k | |
| Com show triggers | 0 | |
| Com show variables | 5 k | |
| Com show warnings | 0 | |
| Com shutdown | 0 | |
| Com signal | 0 | |
| Com start all slaves | 0 | |
| Com start slave | 0 | |
| Com stmt close | 0 | |
| Com stmt execute | 0 | |
| Com stmt fetch | 0 | |
| Com stmt prepare | 0 | |
| Com stmt reprepare | 0 | |
| Com stmt reset | 0 | |
| Com stmt send long data | 0 | |
| Com stop all slaves | 0 | |
| Com stop slave | 0 | |
| Com truncate | 0 | |
| Com uninstall plugin | 0 | |
| Com unlock tables | 0 | |
| Com update | 64 | |
| Com update multi | 0 | |
| Com xa commit | 0 | |
| Com xa end | 0 | |
| Com xa prepare | 0 | |
| Com xa recover | 0 | |
| Com xa rollback | 0 | |
| Com xa start | 0 | |
| Compression | OFF | |
| Connection errors accept | 0 | |
| Connection errors internal | 0 | |
| Connection errors max connections | 0 | |
| Connection errors peer address | 0 | |
| Connection errors select | 0 | |
| Connection errors tcpwrap | 0 | |
| Connections | 24.2 k | The number of connection attempts (successful or not) to the MySQL server. |
| Cpu time | 0 | |
| Created tmp disk tables | 123.2 k | 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 | 5 | How many temporary files mysqld has created. |
| Created tmp tables | 870.9 k | The number of in-memory temporary tables created automatically by the server while executing statements. |
| Delayed errors | 0 | The number of rows written with INSERT DELAYED for which some error occurred (probably duplicate key). |
| Delayed insert threads | 0 | The number of INSERT DELAYED handler threads in use. Every different table on which one uses INSERT DELAYED gets its own thread. |
| Delayed writes | 0 | The number of INSERT DELAYED rows written. |
| Delete scan | 0 | |
| Empty queries | 502.8 k | |
| Executed events | 0 | |
| Executed triggers | 0 | |
| Feature delay key write | 0 | |
| Feature dynamic columns | 0 | |
| Feature fulltext | 0 | |
| Feature gis | 0 | |
| Feature locale | 0 | |
| Feature subquery | 25.8 k | |
| Feature timezone | 0 | |
| Feature trigger | 2.2 k | |
| Feature xml | 0 | |
| Flush commands | 1 | The number of executed FLUSH statements. |
| Handler commit | 1.1 M | The number of internal COMMIT statements. |
| Handler delete | 0 | The number of times a row was deleted from a table. |
| Handler discover | 22.5 k | 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 external lock | 0 | |
| Handler icp attempts | 0 | |
| Handler icp match | 0 | |
| Handler mrr init | 0 | |
| Handler mrr key refills | 0 | |
| Handler mrr rowid refills | 0 | |
| Handler prepare | 0 | |
| Handler read first | 240.4 k | 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 | 878.8 k | 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 | 19 | |
| Handler read next | 1.1 G | 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 | 456 | 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 retry | 0 | |
| Handler read rnd | 1.5 M | 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 deleted | 12.2 k | |
| Handler read rnd next | 22.2 M | 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 | 0 | The number of internal ROLLBACK statements. |
| Handler savepoint | 0 | |
| Handler savepoint rollback | 0 | |
| Handler tmp update | 0 | |
| Handler tmp write | 22 M | |
| Handler update | 2.5 k | The number of requests to update a row in a table. |
| Handler write | 20.2 k | The number of requests to insert a row in a table. |
| Innodb available undo logs | 128 | |
| Innodb background log sync | 5.5 k | |
| Innodb buffer pool bytes data | 191.6 M | |
| Innodb buffer pool bytes dirty | 1.6 M | |
| Innodb buffer pool dump status | Dumping buffer pool(s) not yet started | |
| Innodb buffer pool load status | Loading buffer pool(s) not yet started | |
| Innodb buffer pool pages data | 11.7 k | The number of pages containing data (dirty or clean). |
| Innodb buffer pool pages dirty | 96 | The number of pages currently dirty. |
| Innodb buffer pool pages flushed | 3.6 k | The number of buffer pool pages that have been requested to be flushed. |
| Innodb buffer pool pages free | 21.1 k | The number of free pages. |
| Innodb buffer pool pages lru flushed | 0 | |
| Innodb buffer pool pages made not young | 0 | |
| Innodb buffer pool pages made young | 0 | |
| Innodb buffer pool pages misc | 16 | The number of pages busy because they have been allocated for administrative overhead such as row locks or the adaptive hash index. This value can also be calculated as Innodb_buffer_pool_pages_total - Innodb_buffer_pool_pages_free - Innodb_buffer_pool_pages_data. |
| Innodb buffer pool pages old | 4.3 k | |
| Innodb buffer pool pages total | 32.8 k | Total size of buffer pool, in pages. |
| Innodb buffer pool read ahead | 4.8 k | |
| Innodb buffer pool read ahead evicted | 0 | |
| Innodb buffer pool read ahead rnd | 0 | The number of "random" read-aheads InnoDB initiated. This happens when a query is to scan a large portion of a table but in random order. |
| Innodb buffer pool read requests | 161.7 M | The number of logical read requests InnoDB has done. |
| Innodb buffer pool reads | 6.7 k | The number of logical reads that InnoDB could not satisfy from buffer pool and had to do a single-page read. |
| Innodb buffer pool wait free | 0 | Normally, writes to the InnoDB buffer pool happen in the background. However, if it's necessary to read or create a page and no clean pages are available, it's necessary to wait for pages to be flushed first. This counter counts instances of these waits. If the buffer pool size was set properly, this value should be small. |
| Innodb buffer pool write requests | 30.3 k | The number writes done to the InnoDB buffer pool. |
| Innodb checkpoint age | 65 k | |
| Innodb checkpoint max age | 7.8 M | |
| Innodb data fsyncs | 7.3 k | The number of fsync() operations so far. |
| Innodb data pending fsyncs | 0 | The current number of pending fsync() operations. |
| Innodb data pending reads | 0 | The current number of pending reads. |
| Innodb data pending writes | 0 | The current number of pending writes. |
| Innodb data read | 213.8 M | The amount of data read so far, in bytes. |
| Innodb data reads | 11 k | The total number of data reads. |
| Innodb data writes | 9.3 k | The total number of data writes. |
| Innodb data written | 127.9 M | The amount of data written so far, in bytes. |
| Innodb dblwr pages written | 3.6 k | The number of pages that have been written for doublewrite operations. |
| Innodb dblwr writes | 69 | The number of doublewrite operations that have been performed. |
| Innodb deadlocks | 0 | |
| Innodb have atomic builtins | ON | |
| Innodb history list length | 1.3 k | |
| Innodb ibuf discarded delete marks | 0 | |
| Innodb ibuf discarded deletes | 0 | |
| Innodb ibuf discarded inserts | 0 | |
| Innodb ibuf free list | 224 | |
| Innodb ibuf merged delete marks | 0 | |
| Innodb ibuf merged deletes | 0 | |
| Innodb ibuf merged inserts | 0 | |
| Innodb ibuf merges | 0 | |
| Innodb ibuf segment size | 226 | |
| Innodb ibuf size | 1 | |
| Innodb log waits | 0 | The number of waits we had because log buffer was too small and we had to wait for it to be flushed before continuing. |
| Innodb log write requests | 5.8 k | The number of log write requests. |
| Innodb log writes | 7 k | The number of physical writes to the log file. |
| Innodb lsn current | 22.6 G | |
| Innodb lsn flushed | 22.6 G | |
| Innodb lsn last checkpoint | 22.6 G | |
| Innodb master thread active loops | 5.5 k | |
| Innodb master thread idle loops | 54 | |
| Innodb max trx id | 1.7 G | |
| Innodb mem adaptive hash | 9.1 M | |
| Innodb mem dictionary | 10.5 M | |
| Innodb mem total | 563.1 M | |
| Innodb mutex os waits | 33.4 k | |
| Innodb mutex spin rounds | 1.3 M | |
| Innodb mutex spin waits | 41.3 k | |
| Innodb oldest view low limit trx id | 0 | |
| Innodb os log fsyncs | 7.1 k | The number of fsync() writes done to the log file. |
| Innodb os log pending fsyncs | 0 | The number of pending log file fsyncs. |
| Innodb os log pending writes | 0 | Pending log file writes. |
| Innodb os log written | 6.2 M | The number of bytes written to the log file. |
| Innodb page size | 16.4 k | The compiled-in InnoDB page size (default 16KB). Many values are counted in pages; the page size allows them to be easily converted to bytes. |
| Innodb pages created | 117 | The number of pages created. |
| Innodb pages read | 11.6 k | The number of pages read. |
| Innodb pages0 read | 2.7 k | |
| Innodb pages written | 3.6 k | The number of pages written. |
| Innodb purge trx id | 1.7 G | |
| Innodb purge undo no | 0 | |
| Innodb read views memory | 1.2 k | |
| Innodb row lock current waits | 0 | The number of row locks currently being waited for. |
| Innodb row lock time | 0 | The total time spent in acquiring row locks, in milliseconds. |
| Innodb row lock time avg | 0 | The average time to acquire a row lock, in milliseconds. |
| Innodb row lock time max | 0 | The maximum time to acquire a row lock, in milliseconds. |
| Innodb row lock waits | 0 | The number of times a row lock had to be waited for. |
| Innodb rows deleted | 0 | The number of rows deleted from InnoDB tables. |
| Innodb rows inserted | 0 | The number of rows inserted in InnoDB tables. |
| Innodb rows read | 1.1 G | The number of rows read from InnoDB tables. |
| Innodb rows updated | 2.5 k | The number of rows updated in InnoDB tables. |
| Innodb system rows deleted | 0 | |
| Innodb system rows inserted | 0 | |
| Innodb system rows read | 759 | |
| Innodb system rows updated | 0 | |
| Innodb s lock os waits | 237 | |
| Innodb s lock spin rounds | 11.2 k | |
| Innodb s lock spin waits | 375 | |
| Innodb truncated status writes | 0 | |
| Innodb x lock os waits | 134 | |
| Innodb x lock spin rounds | 4.6 k | |
| Innodb x lock spin waits | 49 | |
| Innodb page compression saved | 0 | |
| Innodb page compression trim sect512 | 0 | |
| Innodb page compression trim sect1024 | 0 | |
| Innodb page compression trim sect2048 | 0 | |
| Innodb page compression trim sect4096 | 0 | |
| Innodb page compression trim sect8192 | 0 | |
| Innodb page compression trim sect16384 | 0 | |
| Innodb page compression trim sect32768 | 0 | |
| Innodb num index pages written | 59 | |
| Innodb num non index pages written | 10.8 k | |
| Innodb num pages page compressed | 0 | |
| Innodb num page compressed trim op | 0 | |
| Innodb num page compressed trim op saved | 0 | |
| Innodb num pages page decompressed | 0 | |
| Innodb num pages page compression error | 0 | |
| Innodb num pages encrypted | 0 | |
| Innodb num pages decrypted | 0 | |
| Innodb have lz4 | OFF | |
| Innodb have lzo | OFF | |
| Innodb have lzma | OFF | |
| Innodb have bzip2 | ON | |
| Innodb have snappy | OFF | |
| Innodb defragment compression failures | 0 | |
| Innodb defragment failures | 0 | |
| Innodb defragment count | 0 | |
| Innodb onlineddl rowlog rows | 0 | |
| Innodb onlineddl rowlog pct used | 0 | |
| Innodb onlineddl pct progress | 0 | |
| Innodb secondary index triggered cluster reads | 0 | |
| Innodb secondary index triggered cluster reads avoided | 0 | |
| Innodb encryption rotation pages read from cache | 0 | |
| Innodb encryption rotation pages read from disk | 0 | |
| Innodb encryption rotation pages modified | 0 | |
| Innodb encryption rotation pages flushed | 0 | |
| Innodb encryption rotation estimated iops | 0 | |
| Innodb scrub background page reorganizations | 0 | |
| Innodb scrub background page splits | 0 | |
| Innodb scrub background page split failures underflow | 0 | |
| Innodb scrub background page split failures out of filespace | 0 | |
| Innodb scrub background page split failures missing index | 0 | |
| Innodb scrub background page split failures unknown | 0 | |
| Key blocks not flushed | 0 | 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 | 13.4 k | 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 | 21 | 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 blocks warm | 0 | |
| Key read requests | 394.9 k | The number of requests to read a key block from the cache. |
| Key reads | 84.7 k | 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 | 0 | The number of requests to write a key block to the cache. |
| Key writes | 0 | The number of physical writes of a key block to disk. |
| Last query cost | 0 | 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. |
| Master gtid wait count | 0 | |
| Master gtid wait time | 0 | |
| Master gtid wait timeouts | 0 | |
| Max statement time exceeded | 0 | |
| Max used connections | 51 | The maximum number of connections that have been in use simultaneously since the server started. |
| Memory used | 173 M | |
| Not flushed delayed rows | 0 | The number of rows waiting to be written in INSERT DELAYED queues. |
| Open files | 27 | The number of files that are open. |
| Open streams | 0 | The number of streams that are open (used mainly for logging). |
| Open table definitions | 400 | |
| Open tables | 64 | The number of tables that are open. |
| Opened files | 4.4 M | |
| Opened plugin libraries | 0 | |
| Opened table definitions | 2.8 M | |
| Opened tables | 3 M | The number of tables that have been opened. If opened tables is big, your table cache value is probably too small. |
| Opened views | 4.2 k | |
| Performance schema accounts lost | 0 | |
| Performance schema cond classes lost | 0 | |
| Performance schema cond instances lost | 0 | |
| Performance schema digest lost | 0 | |
| Performance schema file classes lost | 0 | |
| Performance schema file handles lost | 0 | |
| Performance schema file instances lost | 0 | |
| Performance schema hosts lost | 0 | |
| Performance schema locker lost | 0 | |
| Performance schema mutex classes lost | 0 | |
| Performance schema mutex instances lost | 0 | |
| Performance schema rwlock classes lost | 0 | |
| Performance schema rwlock instances lost | 0 | |
| Performance schema session connect attrs lost | 0 | |
| Performance schema socket classes lost | 0 | |
| Performance schema socket instances lost | 0 | |
| Performance schema stage classes lost | 0 | |
| Performance schema statement classes lost | 0 | |
| Performance schema table handles lost | 0 | |
| Performance schema table instances lost | 0 | |
| Performance schema thread classes lost | 0 | |
| Performance schema thread instances lost | 0 | |
| Performance schema users lost | 0 | |
| Prepared stmt count | 0 | |
| Qcache free blocks | 1 | 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 | 1 M | The amount of free memory for query cache. |
| Qcache hits | 0 | The number of cache hits. |
| Qcache inserts | 0 | The number of queries added to the cache. |
| Qcache lowmem prunes | 0 | 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 | 0 | The number of non-cached queries (not cachable, or not cached due to the query_cache_type setting). |
| Qcache queries in cache | 0 | The number of queries registered in the cache. |
| Qcache total blocks | 1 | The total number of blocks in the query cache. |
| Queries | 2 M | |
| Questions | 2 M | |
| Rows read | 1.1 G | |
| Rows sent | 14.7 M | |
| Rows tmp read | 22.6 M | |
| Rpl status | AUTH_MASTER | The status of failsafe replication (not yet implemented). |
| Select full join | 12.1 k | 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 | 0 | The number of joins that used a range search on a reference table. |
| Select range | 0 | The number of joins that used ranges on the first table. (It's normally not critical even if this is big.) |
| Select range check | 0 | 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 | 960.4 k | The number of joins that did a full scan of the first table. |
| Slave connections | 0 | |
| Slave heartbeat period | 0 | |
| Slave open temp tables | 0 | The number of temporary tables currently open by the slave SQL thread. |
| Slave received heartbeats | 0 | |
| Slave retried transactions | 0 | Total (since startup) number of times the replication slave SQL thread has retried transactions. |
| Slave running | OFF | This is ON if this server is a slave that is connected to a master. |
| Slave skipped errors | 0 | |
| Slaves connected | 0 | |
| Slaves running | 0 | |
| Slow launch threads | 0 | The number of threads that have taken more than slow_launch_time seconds to create. |
| Slow queries | 0 | The number of queries that have taken more than long_query_time seconds. |
| Sort merge passes | 0 | 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 priority queue sorts | 1.8 k | |
| Sort range | 289 | The number of sorts that were done with ranges. |
| Sort rows | 1.5 M | The number of sorted rows. |
| Sort scan | 324.2 k | The number of sorts that were done by scanning the table. |
| Ssl accept renegotiates | 0 | |
| Ssl accepts | 0 | |
| Ssl callback cache hits | 0 | |
| Ssl cipher | ||
| Ssl cipher list | ||
| Ssl client connects | 0 | |
| Ssl connect renegotiates | 0 | |
| Ssl ctx verify depth | 0 | |
| Ssl ctx verify mode | 0 | |
| Ssl default timeout | 0 | |
| Ssl finished accepts | 0 | |
| Ssl finished connects | 0 | |
| Ssl server not after | ||
| Ssl server not before | ||
| Ssl session cache hits | 0 | |
| Ssl session cache misses | 0 | |
| Ssl session cache mode | NONE | |
| Ssl session cache overflows | 0 | |
| Ssl session cache size | 0 | |
| Ssl session cache timeouts | 0 | |
| Ssl sessions reused | 0 | |
| Ssl used session cache entries | 0 | |
| Ssl verify depth | 0 | |
| Ssl verify mode | 0 | |
| Ssl version | ||
| Subquery cache hit | 0 | |
| Subquery cache miss | 0 | |
| Syncs | 6.7 k | |
| Table locks immediate | 1.3 M | The number of times that a table lock was acquired immediately. |
| Table locks waited | 2 | 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 | 0 | |
| Tc log page size | 4.1 k | |
| Tc log page waits | 0 | |
| Threadpool idle threads | 0 | |
| Threadpool threads | 0 | |
| Threads cached | 0 | 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 | 14 | The number of currently open connections. |
| Threads created | 24.2 k | 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 | 4 | The number of threads that are not sleeping. |
| Update scan | 0 | |
| Uptime | 0 days, 1 hours, 32 minutes and 40 seconds | |
| Uptime since flush status | 0 days, 1 hours, 32 minutes and 40 seconds | |
| wsrep cluster conf id | 18.4 E | |
| wsrep cluster size | 0 | |
| wsrep cluster state uuid | ||
| wsrep cluster status | Disconnected | |
| wsrep connected | OFF | |
| wsrep local bf aborts | 0 | |
| wsrep local index | 18.4 E | |
| wsrep provider name | ||
| wsrep provider vendor | ||
| wsrep provider version | ||
| wsrep ready | OFF | |
| wsrep thread count | 0 | |
| Key buffer fraction % | 18.28 % | Percentage of used key cache (calculated value) |
| Key read ratio % | 21.45 % | Key cache miss calculated as rate of physical reads compared to read requests (calculated value) |
| Threads cache hitrate % | 0.01 % | Thread cache hit rate (calculated value) |