localhost

Runtime Information

This MySQL server has been running for 47 days, 0 hours, 18 minutes and 9 seconds. It started up on Sep 14, 2024 at 11:11 PM.

Server traffic: These tables show the network traffic statistics of this MySQL server since its startup.

Traffic 1 ø per hour
Received 2,519 MiB 2,287 KiB
Sent 46 GiB 41 MiB
Total 48 GiB 44 MiB
Connections ø per hour %
max. concurrent connections 8 --- ---
Failed attempts 4 3.55 m 0.00%
Aborted 0 0.00 0.00%
Total 5,881 k 5,212.50 100.00%

Query statistics: Since its startup, 43,759,925 queries have been sent to the server.

Total ø per hour ø per minute ø per second
44 M 38.78 k 646.40 10.77
Query type ø per hour %
set option 12 M 10.433 k 31.08%
select 6,164 k 5.463 k 16.27%
change db 4,882 k 4.327 k 12.89%
show binlogs 4,206 k 3.728 k 11.10%
show tables 1,123 k 995.159 2.96%
show charsets 880 k 779.898 2.32%
show collations 880 k 779.898 2.32%
show plugins 880 k 779.895 2.32%
show variables 842 k 746.602 2.22%
show storage engines 765 k 678.111 2.02%
show master status 689 k 611.091 1.82%
show slave status 689 k 611.091 1.82%
Query type ø per hour %
update 376 k 333.600 0.99%
delete 325 k 287.660 0.86%
show grants 304 k 269.639 0.80%
show processlist 275 k 244.165 0.73%
show status 273 k 241.585 0.72%
insert 163 k 144.441 0.43%
show fields 18 k 15.609 0.05%
show table status 17 k 15.423 0.05%
show create table 11 k 9.606 0.03%
optimize 4,803 4.257 0.01%
show keys 4,007 3.551 0.01%
show triggers 3,226 2.859 0.01%
Query type ø per hour %
show databases 920 0.815 0.00%
kill 557 0.494 0.00%
flush 522 0.463 0.00%
show open tables 201 0.178 0.00%
alter table 152 0.135 0.00%
show create db 94 0.083 0.00%
admin commands 49 0.043 0.00%
unlock tables 47 0.042 0.00%
begin 47 0.042 0.00%
check 8 0.007 0.00%
repair 3 0.003 0.00%
analyze 3 0.003 0.00%
Begin SQL query
Variable Value Description
Flush_commands 99 The number of executed FLUSH statements.
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.
Slow_queries 0 The number of queries that have taken more than long_query_time seconds.Documentation
Begin InnoDB
Variable Value Description
Variables InnoDB Status Documentation
Innodb_buffer_pool_pages_data 1,758 The number of pages containing data (dirty or clean).
Innodb_buffer_pool_bytes_data 29 M
Innodb_buffer_pool_pages_dirty 0 The number of pages currently dirty.
Innodb_buffer_pool_bytes_dirty 0
Innodb_buffer_pool_pages_flushed 42 k The number of buffer pool pages that have been requested to be flushed.
Innodb_buffer_pool_pages_free 6,431 The number of free pages.
Innodb_buffer_pool_pages_misc 2 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 8,191 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 0
Innodb_buffer_pool_read_ahead_evicted 0
Innodb_buffer_pool_read_requests 25 M The number of logical read requests InnoDB has done.
Innodb_buffer_pool_reads 971 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 11 M The number writes done to the InnoDB buffer pool.
Innodb_data_fsyncs 3,945 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 20 M The amount of data read so far, in bytes.
Innodb_data_reads 1,109 The total number of data reads.
Innodb_data_writes 46 k The total number of data writes.
Innodb_data_written 2,001 M The amount of data written so far, in bytes.
Innodb_dblwr_pages_written 42 k The number of pages that have been written for doublewrite operations.
Innodb_dblwr_writes 930 The number of doublewrite operations that have been performed.
Innodb_have_atomic_builtins ON
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,423 k The number of log write requests.
Innodb_log_writes 2,077 The number of physical writes to the log file.
Innodb_os_log_fsyncs 2,089 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 618 M The number of bytes written to the log file.
Innodb_page_size 16 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 788 The number of pages created.
Innodb_pages_read 970 The number of pages read.
Innodb_pages_written 42 k The number of pages written.
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 906 k The number of rows inserted in InnoDB tables.
Innodb_rows_read 1,832 k The number of rows read from InnoDB tables.
Innodb_rows_updated 0 The number of rows updated in InnoDB tables.
Innodb_truncated_status_writes 0
Begin SSL
Variable Value Description
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_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
Begin Handler
Variable Value Description
Handler_commit 1,370 The number of internal COMMIT statements.
Handler_delete 147 k 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_prepare 0
Handler_read_first 6,840 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 8,113 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 1,118 k
Handler_read_next 1,726 M 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 3,838 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 15 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_next 583 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 47 The number of internal ROLLBACK statements.
Handler_savepoint 0
Handler_savepoint_rollback 0
Handler_update 242 k The number of requests to update a row in a table.
Handler_write 562 M The number of requests to insert a row in a table.
Begin Query cache
Variable Value Description
Flush query cache Documentation
Qcache_free_blocks 69 The number of free memory blocks in query cache.
Qcache_free_memory 15 M The amount of free memory for query cache.
Qcache_hits 26 k The number of cache hits.
Qcache_inserts 10 k 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 148 k The number of non-cached queries (not cachable, or not cached due to the query_cache_type setting).
Qcache_queries_in_cache 423 The number of queries registered in the cache.
Qcache_total_blocks 942 The total number of blocks in the query cache.
Begin Threads
Variable Value Description
Show processes Documentation
Slow_launch_threads 0 The number of threads that have taken more than slow_launch_time seconds to create.
Threads_cached 7 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 1 The number of currently open connections.
Threads_created 316 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 The number of threads that are not sleeping.
Threads_cache_hitrate_% 99.99 %
Begin Binary log
Variable Value Description
Documentation
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.
Begin Temporary data
Variable Value Description
Created_tmp_disk_tables 907 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 0 How many temporary files mysqld has created.
Created_tmp_tables 9,036 k The number of in-memory temporary tables created automatically by the server while executing statements.
Begin Delayed inserts
Variable Value Description
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.
Not_flushed_delayed_rows 0 The number of rows waiting to be written in INSERT DELAYED queues.
Begin Key cache
Variable Value Description
Documentation
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 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 4,619 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,794 k The number of requests to read a key block from the cache.
Key_reads 756 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 32 k The number of requests to write a key block to the cache.
Key_writes 19 k The number of physical writes of a key block to disk.
Key_buffer_fraction_% 20.62 %
Key_write_ratio_% 58.73 %
Key_read_ratio_% 0.04 %
Begin Joins
Variable Value Description
Select_full_join 0 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 1,265 k 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 9,039 k The number of joins that did a full scan of the first table.
Begin Replication
Variable Value Description
Documentation
Rpl_status AUTH_MASTER The status of failsafe replication (not yet implemented).
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.
Begin Sorting
Variable Value Description
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_range 20 k The number of sorts that were done with ranges.
Sort_rows 15 M The number of sorted rows.
Sort_scan 3,347 k The number of sorts that were done by scanning the table.
Begin Tables
Variable Value Description
Flush (close) all tables Show open tables
Open_tables 85 The number of tables that are open.
Opened_tables 8,285 The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
Table_locks_immediate 265 k The number of times that a table lock was acquired immediately.
Table_locks_waited 1 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.
Begin Transaction coordinator
Variable Value Description
Tc_log_max_pages_used 0
Tc_log_page_size 0
Tc_log_page_waits 0
Begin
Variable Value Description
Binlog_stmt_cache_disk_use 0
Binlog_stmt_cache_use 0
Compression OFF
Open_files 152 The number of files that are open.
Open_streams 0 The number of streams that are open (used mainly for logging).
Open_table_definitions 82
Opened_files 3,684 k
Opened_table_definitions 8,378
Performance_schema_cond_classes_lost 0
Performance_schema_cond_instances_lost 0
Performance_schema_file_classes_lost 0
Performance_schema_file_handles_lost 0
Performance_schema_file_instances_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_table_handles_lost 0
Performance_schema_table_instances_lost 0
Performance_schema_thread_classes_lost 0
Performance_schema_thread_instances_lost 0
Prepared_stmt_count 0
Queries 44 M
Uptime_since_flush_status 1 days, 16 hours, 58 minutes and 45 seconds
1 On a busy server, the byte counters may overrun, so those statistics as reported by the MySQL server may be incorrect.