In the plugin’s About tab this section shows some information about the site’s MySQL or MariaDB database server. It looks like this.
Here are explanations of the items in this section.
This database server [localhost] up for: 14.6d (since Wed 13-Dec-2023 3:03 am).
This shows the hostname of the database server and how long since it was last rebooted.
This site’s database size: 23MiB. 58.4% data, 41.6% keys.
This shows how much SSD / HDD space is needed for the database server to store this site’s tables. The space is divided between data and keys. High-performance keys take more space than standard keys, so you should expect their percentage to go up when you add them.
All 6 databases size: 68MiB. 81.6% data, 18.4% keys.
This shows how many databases are visible on the server and how much space they take.
Shared database servers may contain more than these 6 databases.
On shared servers, there may be other databases than the visible ones. Some hosting services put many customers on a single database server.
Database buffer pool size: 10GiB. 98.4% used, 1.3% dirty.
This shows the all-important innodb_buffer_pool_size system variable setting. It also shows the server’s global status variables Innodb_buffer_pool_bytes_data and Innodb_buffer_pool_bytes_dirty as fractions of the total buffer pool size. Ideally this will hold a significant fraction of your site’s database size. On shared servers it may be much larger than what is needed for your site alone.
Number of connections to database server: current: 13 limit: 500.
This shows the number of connections (from php processes running WordPress, and possibly from phpmyadmin or other database client programs. At times of high traffic you may see many concurrent connections. If you see a number of connections near the limit it may mean the database server is overloaded.
Minimum database query round-trip time: 221μs.
It takes time for WordPress to send a query to the database and get a response. This item measure how long it takes to send a trivial query (SELECT 1) and get a response. A long time — longer than a few milliseconds — here may mean the database server is overloaded
Temporary results tables used (since 13-Dec-2023): 112.9/sec.
Many MySQL and MariaDB queries create internal temporary tables and use them on the fly to generate results. This is a normal part of fulfilling queries, even optimized ones. Execution plans call this “Using temporary” and sometimes misleadingly call it “Using filesort”. The number shown here is the Created_tmp_tables global status variable in the database server, divided by the amount of time the server has been running.
14.4% overflowed to SSD/HDD.
The database server handles most internal temporary tables entirely in RAM. Some of them spill to SSD or HDD disk files, however. This shows the percentage using disk files, based on the Created_tmp_disk_tables global status variable. Several factors cause the server to spill a temporary table to disk, including the presence of large text columns in the result set.
Database server network traffic (since Wed 13-Dec-2023): 14MiB/sec sent to WordPress, 0.6MiB/sec received
This shows the average network traffic the database server sends to its connections, and the traffic it receives from its connections.