- There are no recent tables.
- There are no favorite tables.
Drop files here
Console
| Variable | Value | Description |
|---|---|---|
| Aborted clients | 150.6 k | The number of connections that were aborted because the client died without closing the connection properly. |
| Aborted connects | 131.5 k | The number of failed attempts to connect to the MySQL server. |
| Binlog cache disk use | 245 | 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 | 31.6 M | The number of transactions that used the temporary binary log cache. |
| Binlog stmt cache disk use | 0 | |
| Binlog stmt cache use | 1.4 M | |
| Bytes received | 592.3 G | |
| Bytes sent | 17.4 T | |
| Com admin commands | 1 M | |
| Com assign to keycache | 0 | |
| Com alter db | 0 | |
| Com alter db upgrade | 0 | |
| Com alter event | 0 | |
| Com alter function | 0 | |
| Com alter instance | 0 | |
| Com alter procedure | 0 | |
| Com alter server | 0 | |
| Com alter table | 125.4 k | |
| Com alter tablespace | 0 | |
| Com alter user | 19 k | |
| Com analyze | 0 | |
| Com begin | 111.7 M | |
| Com binlog | 0 | |
| Com call procedure | 0 | |
| Com change db | 24.8 M | |
| Com change master | 0 | |
| Com change repl filter | 0 | |
| Com check | 0 | |
| Com checksum | 697 | |
| Com commit | 111.6 M | |
| Com create db | 359 | |
| Com create event | 0 | |
| Com create function | 3 | |
| Com create index | 57 | |
| Com create procedure | 0 | |
| Com create server | 0 | |
| Com create table | 4.4 M | |
| Com create trigger | 24 | |
| Com create udf | 0 | |
| Com create user | 2.9 k | |
| Com create view | 4 | |
| Com delete | 21.8 M | |
| Com delete multi | 391.7 k | |
| Com do | 45 k | |
| Com drop db | 31 | |
| Com drop event | 0 | |
| Com drop function | 3 | |
| Com drop index | 7 | |
| Com drop procedure | 0 | |
| Com drop server | 0 | |
| Com drop table | 61.4 k | |
| Com drop trigger | 0 | |
| Com drop user | 2.3 k | |
| Com drop view | 4 | |
| Com empty query | 1.1 k | |
| Com explain other | 0 | |
| Com flush | 7 | |
| Com get diagnostics | 0 | |
| Com grant | 14 k | |
| Com ha close | 0 | |
| Com ha open | 0 | |
| Com ha read | 0 | |
| Com help | 0 | |
| Com insert | 54.3 M | |
| Com insert select | 259.8 k | |
| Com install plugin | 0 | |
| Com kill | 0 | |
| Com load | 0 | |
| Com lock tables | 134.8 k | |
| Com optimize | 7.2 k | |
| Com preload keys | 0 | |
| Com purge | 190 | |
| Com purge before date | 0 | |
| Com release savepoint | 90 k | |
| Com rename table | 2 | |
| Com rename user | 0 | |
| Com repair | 5 | |
| Com replace | 134 k | |
| Com replace select | 0 | |
| Com reset | 1 | |
| Com resignal | 0 | |
| Com revoke | 5.6 k | |
| Com revoke all | 5.8 k | |
| Com rollback | 73.1 k | |
| Com rollback to savepoint | 5.2 M | |
| Com savepoint | 90 k | |
| Com select | 2 G | |
| Com set option | 73.5 M | |
| Com signal | 0 | |
| Com show binlog events | 0 | |
| Com show binlogs | 351.8 k | |
| Com show charsets | 21.1 k | |
| Com show collations | 97 | |
| Com show create db | 89.4 k | |
| Com show create event | 0 | |
| Com show create func | 539 | |
| Com show create proc | 0 | |
| Com show create table | 5.3 M | |
| Com show create trigger | 3 k | |
| Com show databases | 848 | |
| Com show engine logs | 0 | |
| Com show engine mutex | 0 | |
| Com show engine status | 285 k | |
| Com show events | 90 k | |
| Com show errors | 7.5 k | |
| Com show fields | 34.6 M | |
| Com show function code | 0 | |
| Com show function status | 90.2 k | |
| Com show grants | 17.9 k | |
| Com show keys | 60.7 k | |
| Com show master status | 1.3 k | |
| Com show open tables | 0 | |
| Com show plugins | 3.2 k | |
| Com show privileges | 0 | |
| Com show procedure code | 0 | |
| Com show procedure status | 90.2 k | |
| Com show processlist | 18 | |
| Com show profile | 0 | |
| Com show profiles | 0 | |
| Com show relaylog events | 0 | |
| Com show slave hosts | 351 k | |
| Com show slave status | 706.3 k | |
| Com show status | 1.5 M | |
| Com show storage engines | 778 | |
| Com show table status | 10.4 M | |
| Com show tables | 7 M | |
| Com show triggers | 10.4 M | |
| Com show variables | 780.3 k | |
| Com show warnings | 2 k | |
| Com show create user | 0 | |
| Com shutdown | 0 | |
| Com slave start | 0 | |
| Com slave stop | 1 | |
| Com group replication start | 0 | |
| Com group replication stop | 0 | |
| Com stmt execute | 10.3 M | |
| Com stmt close | 10.3 M | |
| Com stmt fetch | 0 | |
| Com stmt prepare | 10.3 M | |
| Com stmt reset | 0 | |
| Com stmt send long data | 71.9 k | |
| Com truncate | 24.9 k | |
| Com uninstall plugin | 0 | |
| Com unlock tables | 229.5 k | |
| Com update | 76.2 M | |
| Com update multi | 535.2 k | |
| Com xa commit | 0 | |
| Com xa end | 0 | |
| Com xa prepare | 0 | |
| Com xa recover | 0 | |
| Com xa rollback | 0 | |
| Com xa start | 0 | |
| Com stmt reprepare | 0 | |
| 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 | 17.1 M | The number of connection attempts (successful or not) to the MySQL server. |
| Created tmp disk tables | 76.2 M | 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 | 3.1 M | How many temporary files mysqld has created. |
| Created tmp tables | 230.6 M | 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. |
| Flush commands | 1 | The number of executed FLUSH statements. |
| Handler commit | 3 G | The number of internal COMMIT statements. |
| Handler delete | 52 M | The number of times a row was deleted from a table. |
| Handler discover | 0 | 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 | 7.2 G | |
| Handler mrr init | 0 | |
| Handler prepare | 64.2 M | |
| Handler read first | 95.5 M | 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 | 34.4 G | 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 | 2.2 M | |
| Handler read next | 115.7 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 | 6.9 G | 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 | 22.2 G | 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 | 65.5 G | 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 | 230.7 k | The number of internal ROLLBACK statements. |
| Handler savepoint | 90 k | |
| Handler savepoint rollback | 5.2 M | |
| Handler update | 2.4 G | The number of requests to update a row in a table. |
| Handler write | 53.8 G | The number of requests to insert a row in a table. |
| Innodb buffer pool dump status | Dumping of buffer pool not started | |
| Innodb buffer pool load status | Buffer pool(s) load completed at 250904 16:39:40 | |
| Innodb buffer pool resize status | ||
| Innodb buffer pool pages data | 767.6 k | The number of pages containing data (dirty or clean). |
| Innodb buffer pool bytes data | 12.6 G | |
| Innodb buffer pool pages dirty | 7.8 k | The number of pages currently dirty. |
| Innodb buffer pool bytes dirty | 127.9 M | |
| Innodb buffer pool pages flushed | 41.5 M | The number of buffer pool pages that have been requested to be flushed. |
| Innodb buffer pool pages free | 254 | The number of free pages. |
| Innodb buffer pool pages misc | 18.5 k | 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 total | 786.4 k | Total size of buffer pool, in pages. |
| 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 ahead | 20.3 M | |
| Innodb buffer pool read ahead evicted | 653.2 k | |
| Innodb buffer pool read requests | 274.7 G | The number of logical read requests InnoDB has done. |
| Innodb buffer pool reads | 85.9 M | 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 | 7.3 G | The number writes done to the InnoDB buffer pool. |
| Innodb data fsyncs | 64.4 M | 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 | 1.7 T | The amount of data read so far, in bytes. |
| Innodb data reads | 106.7 M | The total number of data reads. |
| Innodb data writes | 772.8 M | The total number of data writes. |
| Innodb data written | 3 T | The amount of data written so far, in bytes. |
| Innodb dblwr pages written | 41.8 M | The number of pages that have been written for doublewrite operations. |
| Innodb dblwr writes | 6.4 M | The number of doublewrite operations that have been performed. |
| 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 | 1.8 G | The number of log write requests. |
| Innodb log writes | 722.8 M | The number of physical writes to the log file. |
| Innodb os log fsyncs | 44.6 M | 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 | 1.6 T | 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 | 2.9 M | The number of pages created. |
| Innodb pages read | 106.6 M | The number of pages read. |
| Innodb pages written | 41.8 M | The number of pages written. |
| Innodb row lock current waits | 0 | The number of row locks currently being waited for. |
| Innodb row lock time | 1.6 M | The total time spent in acquiring row locks, in milliseconds. |
| Innodb row lock time avg | 3 | The average time to acquire a row lock, in milliseconds. |
| Innodb row lock time max | 1.2 k | The maximum time to acquire a row lock, in milliseconds. |
| Innodb row lock waits | 487.4 k | The number of times a row lock had to be waited for. |
| Innodb rows deleted | 52 M | The number of rows deleted from InnoDB tables. |
| Innodb rows inserted | 139.1 M | The number of rows inserted in InnoDB tables. |
| Innodb rows read | 177.2 G | The number of rows read from InnoDB tables. |
| Innodb rows updated | 775.4 M | The number of rows updated in InnoDB tables. |
| Innodb num open files | 6 k | |
| Innodb truncated status writes | 0 | |
| Innodb available undo logs | 128 | |
| 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 | 53.6 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 | 2.8 k | 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 | 1.1 G | The number of requests to read a key block from the cache. |
| Key reads | 20.3 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 | 443.4 M | The number of requests to write a key block to the cache. |
| Key writes | 1.7 M | The number of physical writes of a key block to disk. |
| Locked connects | 0 | |
| Max execution time exceeded | 0 | |
| Max execution time set | 34.8 k | |
| Max execution time set failed | 0 | |
| Max used connections | 201 | The maximum number of connections that have been in use simultaneously since the server started. |
| Max used connections time | 2025-12-10 13:55:31 | |
| Not flushed delayed rows | 0 | The number of rows waiting to be written in INSERT DELAYED queues. |
| Ongoing anonymous transaction count | 0 | |
| Open files | 4 | The number of files that are open. |
| Open streams | 0 | The number of streams that are open (used mainly for logging). |
| Open table definitions | 3.4 k | |
| Open tables | 6 k | The number of tables that are open. |
| Opened files | 327.9 M | |
| Opened table definitions | 18.5 M | |
| Opened tables | 85.4 M | The number of tables that have been opened. If opened tables is big, your table cache value is probably too small. |
| Performance schema accounts lost | 0 | |
| Performance schema cond classes lost | 0 | |
| Performance schema cond instances lost | 0 | |
| Performance schema digest lost | 2.2 G | |
| Performance schema file classes lost | 0 | |
| Performance schema file handles lost | 0 | |
| Performance schema file instances lost | 95.6 k | |
| Performance schema hosts lost | 0 | |
| Performance schema index stat lost | 0 | |
| Performance schema locker lost | 0 | |
| Performance schema memory classes lost | 0 | |
| Performance schema metadata lock lost | 0 | |
| Performance schema mutex classes lost | 0 | |
| Performance schema mutex instances lost | 0 | |
| Performance schema nested statement lost | 0 | |
| Performance schema prepared statements lost | 0 | |
| Performance schema program 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 table lock stat 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 | 0 | 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 | 0 | 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 | 0 | The total number of blocks in the query cache. |
| Queries | 2.5 G | |
| Questions | 2.3 G | |
| Rsa public key | -----BEGIN PUBLIC KEY----- MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxWK/UeaRCY3CJZC6JAnl nsX4qEbf+Hv+n/Rfx+M9j1bz4IfBtPu4lChfpTqhJQyngz8nnru5H6t/dM4hSosE J3ZQ2hdgpBEANGMpvIrDOBnXiNYcSUIZ39RYsMAlwyESHYL9IjGeM04bV5AqxHFC 0EUMb0aMQ+csjUNof3W9o+knQUyNCogdZgsFY1hPG4aPmMOQOeIrovl82+AQSEp5 IZq/pW7VrrY7B2dDsFa9PFONbZapyPvG+eHQSyLhwvDd3yFElTjOyICMok7RiCKl uICOVSdubDnBM2jSrCRbQ8rKwWSwojRtmmcUMWQkOoerDwb58GdxGRZZxcD58zaj XQIDAQAB -----END PUBLIC KEY----- | |
| Select full join | 6 M | 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 | 4.8 M | The number of joins that used a range search on a reference table. |
| Select range | 186.7 M | The number of joins that used ranges on the first table. (It's normally not critical even if this is big.) |
| Select range check | 51.7 k | 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 | 157.9 M | The number of joins that did a full scan of the first table. |
| Slave open temp tables | 0 | The number of temporary tables currently open by the slave SQL thread. |
| Slow launch threads | 0 | The number of threads that have taken more than slow_launch_time seconds to create. |
| Slow queries | 1.2 k | The number of queries that have taken more than long_query_time seconds. |
| Sort merge passes | 1.8 M | 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 | 119.5 M | The number of sorts that were done with ranges. |
| Sort rows | 22.9 G | The number of sorted rows. |
| Sort scan | 174.8 M | The number of sorts that were done by scanning the table. |
| Ssl accept renegotiates | 0 | |
| Ssl accepts | 15.3 k | |
| Ssl callback cache hits | 0 | |
| Ssl cipher | ||
| Ssl cipher list | ||
| Ssl client connects | 0 | |
| Ssl connect renegotiates | 0 | |
| Ssl ctx verify depth | 18.4 E | |
| Ssl ctx verify mode | 5 | |
| Ssl default timeout | 0 | |
| Ssl finished accepts | 15.3 k | |
| Ssl finished connects | 0 | |
| Ssl server not after | Aug 12 11:50:10 2026 GMT | |
| Ssl server not before | Aug 12 11:50:11 2025 GMT | |
| Ssl session cache hits | 0 | |
| Ssl session cache misses | 15.3 k | |
| Ssl session cache mode | SERVER | |
| Ssl session cache overflows | 0 | |
| Ssl session cache size | 128 | |
| 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 | ||
| Table locks immediate | 2.2 M | The number of times that a table lock was acquired immediately. |
| Table locks waited | 0 | 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. |
| Table open cache hits | 3.6 G | |
| Table open cache misses | 85.4 M | |
| Table open cache overflows | 85.2 M | |
| Tc log max pages used | 0 | |
| Tc log page size | 0 | |
| Tc log page waits | 0 | |
| Threads cached | 88 | 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 | 15 | The number of currently open connections. |
| Threads created | 230 | 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 | 2 | The number of threads that are not sleeping. |
| Uptime | 97 days, 11 hours, 58 minutes and 38 seconds | |
| Uptime since flush status | 97 days, 11 hours, 58 minutes and 38 seconds | |
| Key buffer fraction % | 18.24 % | Percentage of used key cache (calculated value) |
| Key write ratio % | 0.38 % | Percentage of physical writes compared to write requests (calculated value) |
| Key read ratio % | <0.01 % | Key cache miss calculated as rate of physical reads compared to read requests (calculated value) |
| Threads cache hitrate % | 100.00 % | Thread cache hit rate (calculated value) |