Server: mysql wampserver
Filters
VariableValueDescription
Aborted clientsDocumentation1 The number of connections that were aborted because the client died without closing the connection properly.
Aborted connectsDocumentation32 The number of failed attempts to connect to the MySQL server.
Binlog cache disk useDocumentation0The 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 useDocumentation0The number of transactions that used the temporary binary log cache.
Binlog stmt cache disk useDocumentation0
Binlog stmt cache useDocumentation0
Bytes receivedDocumentation3.7 G
Bytes sentDocumentation15.2 G
Com admin commandsDocumentation0
Com assign to keycacheDocumentation0
Com alter dbDocumentation0
Com alter db upgradeDocumentation0
Com alter eventDocumentation0
Com alter functionDocumentation0
Com alter procedureDocumentation0
Com alter serverDocumentation0
Com alter tableDocumentation0
Com alter tablespaceDocumentation0
Com alter userDocumentation0
Com analyzeDocumentation0
Com beginDocumentation0
Com binlogDocumentation0
Com call procedureDocumentation0
Com change dbDocumentation1.6 M
Com change masterDocumentation0
Com checkDocumentation0
Com checksumDocumentation0
Com commitDocumentation0
Com create dbDocumentation0
Com create eventDocumentation0
Com create functionDocumentation0
Com create indexDocumentation0
Com create procedureDocumentation0
Com create serverDocumentation0
Com create tableDocumentation0
Com create triggerDocumentation0
Com create udfDocumentation0
Com create userDocumentation0
Com create viewDocumentation0
Com deleteDocumentation0
Com delete multiDocumentation0
Com doDocumentation0
Com drop dbDocumentation0
Com drop eventDocumentation0
Com drop functionDocumentation0
Com drop indexDocumentation0
Com drop procedureDocumentation0
Com drop serverDocumentation0
Com drop tableDocumentation0
Com drop triggerDocumentation0
Com drop userDocumentation0
Com drop viewDocumentation0
Com empty queryDocumentation0
Com flushDocumentation0
Com get diagnosticsDocumentation0
Com grantDocumentation0
Com ha closeDocumentation0
Com ha openDocumentation0
Com ha readDocumentation0
Com helpDocumentation0
Com insertDocumentation0
Com insert selectDocumentation0
Com install pluginDocumentation0
Com killDocumentation0
Com loadDocumentation0
Com lock tablesDocumentation0
Com optimizeDocumentation0
Com preload keysDocumentation0
Com purgeDocumentation0
Com purge before dateDocumentation0
Com release savepointDocumentation0
Com rename tableDocumentation0
Com rename userDocumentation0
Com repairDocumentation0
Com replaceDocumentation0
Com replace selectDocumentation0
Com resetDocumentation0
Com resignalDocumentation0
Com revokeDocumentation0
Com revoke allDocumentation0
Com rollbackDocumentation0
Com rollback to savepointDocumentation0
Com savepointDocumentation0
Com selectDocumentation13.1 M
Com set optionDocumentation2.7 M
Com signalDocumentation0
Com show binlog eventsDocumentation0
Com show binlogsDocumentation1.5 M
Com show charsetsDocumentation0
Com show collationsDocumentation0
Com show create dbDocumentation0
Com show create eventDocumentation0
Com show create funcDocumentation0
Com show create procDocumentation0
Com show create tableDocumentation6.5 k
Com show create triggerDocumentation0
Com show databasesDocumentation0
Com show engine logsDocumentation0
Com show engine mutexDocumentation0
Com show engine statusDocumentation0
Com show eventsDocumentation0
Com show errorsDocumentation0
Com show fieldsDocumentation932.9 k
Com show function codeDocumentation0
Com show function statusDocumentation0
Com show grantsDocumentation161.1 k
Com show keysDocumentation392.8 k
Com show master statusDocumentation229.6 k
Com show open tablesDocumentation0
Com show pluginsDocumentation232
Com show privilegesDocumentation0
Com show procedure codeDocumentation0
Com show procedure statusDocumentation0
Com show processlistDocumentation21.4 k
Com show profileDocumentation0
Com show profilesDocumentation0
Com show relaylog eventsDocumentation0
Com show slave hostsDocumentation0
Com show slave statusDocumentation229.6 k
Com show statusDocumentation35.1 k
Com show storage enginesDocumentation41.9 k
Com show table statusDocumentation70.5 k
Com show tablesDocumentation1.9 M
Com show triggersDocumentation0
Com show variablesDocumentation432.5 k
Com show warningsDocumentation0
Com slave startDocumentation0
Com slave stopDocumentation0
Com stmt closeDocumentation0
Com stmt executeDocumentation0
Com stmt fetchDocumentation0
Com stmt prepareDocumentation0
Com stmt reprepareDocumentation0
Com stmt resetDocumentation0
Com stmt send long dataDocumentation0
Com truncateDocumentation0
Com uninstall pluginDocumentation0
Com unlock tablesDocumentation0
Com updateDocumentation0
Com update multiDocumentation0
Com xa commitDocumentation0
Com xa endDocumentation0
Com xa prepareDocumentation0
Com xa recoverDocumentation0
Com xa rollbackDocumentation0
Com xa startDocumentation0
CompressionDocumentationOFF
Connection errors acceptDocumentation0
Connection errors internalDocumentation0
Connection errors max connectionsDocumentation0
Connection errors peer addressDocumentation0
Connection errors selectDocumentation0
Connection errors tcpwrapDocumentation0
ConnectionsDocumentation1.4 MThe number of connection attempts (successful or not) to the MySQL server.
Created tmp disk tablesDocumentation3.6 MThe 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 filesDocumentation5 How many temporary files mysqld has created.
Created tmp tablesDocumentation28.1 MThe number of in-memory temporary tables created automatically by the server while executing statements.
Delayed errorsDocumentation0The number of rows written with INSERT DELAYED for which some error occurred (probably duplicate key).
Delayed insert threadsDocumentation0The number of INSERT DELAYED handler threads in use. Every different table on which one uses INSERT DELAYED gets its own thread.
Delayed writesDocumentation0The number of INSERT DELAYED rows written.
Flush commandsDocumentation1 The number of executed FLUSH statements.
Handler commitDocumentation3.3 kThe number of internal COMMIT statements.
Handler deleteDocumentation0The number of times a row was deleted from a table.
Handler discoverDocumentation0The 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 lockDocumentation1.3 M
Handler mrr initDocumentation0
Handler prepareDocumentation0
Handler read firstDocumentation362.8 kThe 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 keyDocumentation3.3 kThe 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 lastDocumentation0
Handler read nextDocumentation353.5 kThe 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 prevDocumentation0The number of requests to read the previous row in key order. This read method is mainly used to optimize ORDER BY … DESC.
Handler read rndDocumentation18.8 MThe 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 nextDocumentation637 MThe 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 rollbackDocumentation0The number of internal ROLLBACK statements.
Handler savepointDocumentation0
Handler savepoint rollbackDocumentation0
Handler updateDocumentation0The number of requests to update a row in a table.
Handler writeDocumentation622.8 MThe number of requests to insert a row in a table.
Innodb buffer pool dump statusDocumentationnot started
Innodb buffer pool load statusDocumentationnot started
Innodb buffer pool pages dataDocumentation355 The number of pages containing data (dirty or clean).
Innodb buffer pool bytes dataDocumentation5.8 M
Innodb buffer pool pages dirtyDocumentation0The number of pages currently dirty.
Innodb buffer pool bytes dirtyDocumentation0
Innodb buffer pool pages flushedDocumentation13 The number of buffer pool pages that have been requested to be flushed.
Innodb buffer pool pages freeDocumentation7.8 kThe number of free pages.
Innodb buffer pool pages miscDocumentation0The 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 totalDocumentation8.2 kTotal size of buffer pool, in pages.
Innodb buffer pool read ahead rndDocumentation0The 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 aheadDocumentation0
Innodb buffer pool read ahead evictedDocumentation0
Innodb buffer pool read requestsDocumentation3.8 MThe number of logical read requests InnoDB has done.
Innodb buffer pool readsDocumentation356 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 freeDocumentation0Normally, 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 requestsDocumentation13 The number writes done to the InnoDB buffer pool.
Innodb data fsyncsDocumentation53 The number of fsync() operations so far.
Innodb data pending fsyncsDocumentation0The current number of pending fsync() operations.
Innodb data pending readsDocumentation0The current number of pending reads.
Innodb data pending writesDocumentation0The current number of pending writes.
Innodb data readDocumentation5.9 MThe amount of data read so far, in bytes.
Innodb data readsDocumentation375 The total number of data reads.
Innodb data writesDocumentation53 The total number of data writes.
Innodb data writtenDocumentation439.8 kThe amount of data written so far, in bytes.
Innodb dblwr pages writtenDocumentation13 The number of pages that have been written for doublewrite operations.
Innodb dblwr writesDocumentation13 The number of doublewrite operations that have been performed.
Innodb have atomic builtinsDocumentationON
Innodb log waitsDocumentation0The 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 requestsDocumentation0The number of log write requests.
Innodb log writesDocumentation13 The number of physical writes to the log file.
Innodb os log fsyncsDocumentation27 The number of fsync() writes done to the log file.
Innodb os log pending fsyncsDocumentation0The number of pending log file fsyncs.
Innodb os log pending writesDocumentation0Pending log file writes.
Innodb os log writtenDocumentation6.7 kThe number of bytes written to the log file.
Innodb page sizeDocumentation16.4 kThe 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 createdDocumentation0The number of pages created.
Innodb pages readDocumentation355 The number of pages read.
Innodb pages writtenDocumentation13 The number of pages written.
Innodb row lock current waitsDocumentation0The number of row locks currently being waited for.
Innodb row lock timeDocumentation0The total time spent in acquiring row locks, in milliseconds.
Innodb row lock time avgDocumentation0The average time to acquire a row lock, in milliseconds.
Innodb row lock time maxDocumentation0The maximum time to acquire a row lock, in milliseconds.
Innodb row lock waitsDocumentation0The number of times a row lock had to be waited for.
Innodb rows deletedDocumentation0The number of rows deleted from InnoDB tables.
Innodb rows insertedDocumentation0The number of rows inserted in InnoDB tables.
Innodb rows readDocumentation3.3 kThe number of rows read from InnoDB tables.
Innodb rows updatedDocumentation0The number of rows updated in InnoDB tables.
Innodb num open filesDocumentation12
Innodb truncated status writesDocumentation0
Innodb available undo logsDocumentation128
Key blocks not flushedDocumentation0The 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 unusedDocumentation14.3 kThe 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 usedDocumentation5 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 requestsDocumentation352.7 kThe number of requests to read a key block from the cache.
Key readsDocumentation5 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 requestsDocumentation0The number of requests to write a key block to the cache.
Key writesDocumentation0The number of physical writes of a key block to disk.
Last query costDocumentation0The 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.
Last query partial plansDocumentation0
Max used connectionsDocumentation16 The maximum number of connections that have been in use simultaneously since the server started.
Not flushed delayed rowsDocumentation0The number of rows waiting to be written in INSERT DELAYED queues.
Open filesDocumentation80 The number of files that are open.
Open streamsDocumentation0The number of streams that are open (used mainly for logging).
Open table definitionsDocumentation84
Open tablesDocumentation177 The number of tables that are open.
Opened filesDocumentation14.5 M
Opened table definitionsDocumentation84
Opened tablesDocumentation4.3 MThe number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
Performance schema accounts lostDocumentation0
Performance schema cond classes lostDocumentation0
Performance schema cond instances lostDocumentation0
Performance schema digest lostDocumentation0
Performance schema file classes lostDocumentation0
Performance schema file handles lostDocumentation0
Performance schema file instances lostDocumentation0
Performance schema hosts lostDocumentation0
Performance schema locker lostDocumentation0
Performance schema mutex classes lostDocumentation0
Performance schema mutex instances lostDocumentation0
Performance schema rwlock classes lostDocumentation0
Performance schema rwlock instances lostDocumentation0
Performance schema session connect attrs lostDocumentation0
Performance schema socket classes lostDocumentation0
Performance schema socket instances lostDocumentation0
Performance schema stage classes lostDocumentation0
Performance schema statement classes lostDocumentation0
Performance schema table handles lostDocumentation0
Performance schema table instances lostDocumentation0
Performance schema thread classes lostDocumentation0
Performance schema thread instances lostDocumentation0
Performance schema users lostDocumentation0
Prepared stmt countDocumentation0
Qcache free blocksDocumentation1 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 memoryDocumentation1 MThe amount of free memory for query cache.
Qcache hitsDocumentation0The number of cache hits.
Qcache insertsDocumentation0The number of queries added to the cache.
Qcache lowmem prunesDocumentation0The 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 cachedDocumentation13.1 MThe number of non-cached queries (not cachable, or not cached due to the query_cache_type setting).
Qcache queries in cacheDocumentation0The number of queries registered in the cache.
Qcache total blocksDocumentation1 The total number of blocks in the query cache.
QueriesDocumentation24.7 M
QuestionsDocumentation24.7 M
Select full joinDocumentation0The 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 joinDocumentation0The number of joins that used a range search on a reference table.
Select rangeDocumentation0The number of joins that used ranges on the first table. (It's normally not critical even if this is big.)
Select range checkDocumentation0The 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 scanDocumentation14 MThe number of joins that did a full scan of the first table.
Slave heartbeat periodDocumentation0
Slave last heartbeatDocumentation
Slave open temp tablesDocumentation0The number of temporary tables currently open by the slave SQL thread.
Slave received heartbeatsDocumentation0
Slave retried transactionsDocumentation0Total (since startup) number of times the replication slave SQL thread has retried transactions.
Slave runningDocumentationOFFThis is ON if this server is a slave that is connected to a master.
Slow launch threadsDocumentation0The number of threads that have taken more than slow_launch_time seconds to create.
Slow queriesDocumentation3 The number of queries that have taken more than long_query_time seconds.Documentation
Sort merge passesDocumentation0The 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 rangeDocumentation0The number of sorts that were done with ranges.
Sort rowsDocumentation18.8 MThe number of sorted rows.
Sort scanDocumentation2.1 MThe number of sorts that were done by scanning the table.
Ssl accept renegotiatesDocumentation0
Ssl acceptsDocumentation0
Ssl callback cache hitsDocumentation0
Ssl cipherDocumentation
Ssl cipher listDocumentation
Ssl client connectsDocumentation0
Ssl connect renegotiatesDocumentation0
Ssl ctx verify depthDocumentation0
Ssl ctx verify modeDocumentation0
Ssl default timeoutDocumentation0
Ssl finished acceptsDocumentation0
Ssl finished connectsDocumentation0
Ssl server not afterDocumentation
Ssl server not beforeDocumentation
Ssl session cache hitsDocumentation0
Ssl session cache missesDocumentation0
Ssl session cache modeDocumentationNONE
Ssl session cache overflowsDocumentation0
Ssl session cache sizeDocumentation0
Ssl session cache timeoutsDocumentation0
Ssl sessions reusedDocumentation0
Ssl used session cache entriesDocumentation0
Ssl verify depthDocumentation0
Ssl verify modeDocumentation0
Ssl versionDocumentation
Table locks immediateDocumentation639.1 kThe number of times that a table lock was acquired immediately.
Table locks waitedDocumentation0The 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 hitsDocumentation12 M
Table open cache missesDocumentation184
Table open cache overflowsDocumentation0
Tc log max pages usedDocumentation0
Tc log page sizeDocumentation0
Tc log page waitsDocumentation0
Threads cachedDocumentation8 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 connectedDocumentation1 The number of currently open connections.
Threads createdDocumentation292 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 runningDocumentation1 The number of threads that are not sleeping.
UptimeDocumentation3 days, 3 hours, 22 minutes and 4 seconds
Uptime since flush statusDocumentation3 days, 3 hours, 22 minutes and 4 seconds
Key buffer fraction %12.46 %Percentage of used key cache (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 %99.98 %Thread cache hit rate (calculated value)