Letakkan berkas disini
Konsol
| Variabel | Nilai | Deskripsi |
|---|---|---|
| Aborted clients | 284 | The number of connections that were aborted because the client died without closing the connection properly. |
| Aborted connects | 67 | Jumlah upaya koneksi ke server MySQL yang gagal. |
| Aborted connects preauth | 70 | |
| Access denied errors | 0 | |
| Acl column grants | 0 | |
| Acl database grants | 4 | |
| Acl function grants | 0 | |
| Acl procedure grants | 0 | |
| Acl package spec grants | 0 | |
| Acl package body grants | 0 | |
| Acl proxy users | 1 | |
| Acl role grants | 0 | |
| Acl roles | 0 | |
| Acl table grants | 0 | |
| Acl users | 7 | |
| Aria pagecache blocks not flushed | 0 | |
| Aria pagecache blocks unused | 15.7 k | |
| Aria pagecache blocks used | 7.8 k | |
| Aria pagecache read requests | 66 M | |
| Aria pagecache reads | 5.3 M | |
| Aria pagecache write requests | 10.9 M | |
| Aria pagecache writes | 10.9 M | |
| Aria transaction log syncs | 6.7 k | |
| 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 | Jumlah transaksi yang menggunakan singgahan log biner temporer, namun melebihi nilai binlog_cache_size dan menggunakan berkas temporer untuk menyimpan perintah dari transaksi. |
| Binlog cache use | 0 | Jumlah transaksi yang menggunakan singgahan log biner temporer. |
| Binlog stmt cache disk use | 0 | |
| Binlog stmt cache use | 0 | |
| Busy time | 0 | |
| Bytes received | 14.4 G | |
| Bytes sent | 47.8 G | |
| Column compressions | 0 | |
| Column decompressions | 0 | |
| Com admin commands | 291.5 k | |
| 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 sequence | 0 | |
| Com alter table | 0 | |
| Com alter tablespace | 0 | |
| Com alter user | 0 | |
| Com analyze | 0 | |
| Com assign to keycache | 0 | |
| Com backup | 0 | |
| Com backup lock | 0 | |
| Com begin | 0 | |
| Com binlog | 0 | |
| Com call procedure | 0 | |
| Com change db | 7 M | |
| Com change master | 0 | |
| Com check | 0 | |
| Com checksum | 0 | |
| Com commit | 4 k | |
| Com compound sql | 0 | |
| Com create db | 0 | |
| Com create event | 0 | |
| Com create function | 0 | |
| Com create index | 0 | |
| Com create package | 0 | |
| Com create package body | 0 | |
| Com create procedure | 0 | |
| Com create role | 0 | |
| Com create sequence | 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 | 112.6 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 package | 0 | |
| Com drop package body | 0 | |
| Com drop role | 0 | |
| Com drop server | 0 | |
| Com drop sequence | 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 execute immediate | 0 | |
| Com flush | 9 | |
| 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 | 491.6 k | |
| Com insert select | 0 | |
| Com install plugin | 0 | |
| Com kill | 0 | |
| Com load | 0 | |
| Com lock tables | 7 | |
| Com multi | 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 | 613.2 k | |
| Com replace select | 0 | |
| Com reset | 0 | |
| Com resignal | 0 | |
| Com revoke | 0 | |
| Com revoke all | 0 | |
| Com revoke role | 0 | |
| Com rollback | 14 | |
| Com rollback to savepoint | 0 | |
| Com savepoint | 0 | |
| Com select | 88 M | |
| Com set option | 4.1 M | |
| Com show authors | 0 | |
| Com show binlog events | 0 | |
| Com show binlogs | 9.4 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 package | 0 | |
| Com show create package body | 0 | |
| Com show create proc | 14 | |
| Com show create table | 1.2 M | |
| Com show create trigger | 0 | |
| Com show create user | 0 | |
| Com show databases | 1 | |
| Com show engine logs | 0 | |
| Com show engine mutex | 0 | |
| Com show engine status | 2 | |
| Com show errors | 0 | |
| Com show events | 0 | |
| Com show explain | 0 | |
| Com show fields | 4.9 M | |
| Com show function status | 0 | |
| Com show generic | 0 | |
| Com show grants | 1.2 M | |
| Com show keys | 5.5 M | |
| Com show master status | 730 | |
| Com show open tables | 0 | |
| Com show package status | 0 | |
| Com show package body status | 0 | |
| Com show plugins | 0 | |
| Com show privileges | 0 | |
| Com show procedure status | 0 | |
| Com show processlist | 9 | |
| Com show profile | 0 | |
| Com show profiles | 0 | |
| Com show relaylog events | 0 | |
| Com show slave hosts | 0 | |
| Com show slave status | 744 | |
| Com show status | 72 | |
| Com show storage engines | 20.6 k | |
| Com show table status | 26.9 k | |
| Com show tables | 1.6 M | |
| Com show triggers | 0 | |
| Com show variables | 2.1 M | |
| Com show warnings | 1 M | |
| 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 | 7 | |
| Com update | 28.5 k | |
| 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 | 7.2 M | Jumlah upaya koneksi ke server MySQL (baik berhasil maupun tidak). |
| Cpu time | 0 | |
| Created tmp disk tables | 5.3 M | Jumlah tabel temporer pada diska yang dibuat otomatis oleh server saat mengeksekusi perintah. Bila Created_tmp_disk_tables ukurannya besar, anda mungkin perlu meningkatkan nilai tmp_table_size agar tabel temporer disimpan di yang berbasis memori daripada yang berbasis diska. |
| Created tmp files | 4 | Jumlah berkas temporer yang telah dibuat mysqld. |
| Created tmp tables | 80.8 M | Jumlah tabel temporer dalam-memori yang dibuat otomatis oleh server sewaktu mengeksekusi perintah. |
| Delayed errors | 0 | Jumlah baris yang ditulis oleh INSERT DELAYED yang menyebabkan beberapa galat (kemungkinan karena kunci duplikat). |
| Delayed insert threads | 0 | Jumlah thread handler INSERT DELAYED yang dipakai. Setiap tabel berbeda yang menggunakan INSERT DELAYED mendapat satu thread sendiri. |
| Delayed writes | 0 | Jumlah baris INSERT DELAYED yang ditulis. |
| Delete scan | 1.9 k | |
| Empty queries | 42.4 M | |
| Executed events | 0 | |
| Executed triggers | 0 | |
| Feature application time periods | 0 | |
| Feature check constraint | 168 | |
| Feature custom aggregate functions | 0 | |
| Feature delay key write | 0 | |
| Feature dynamic columns | 0 | |
| Feature fulltext | 0 | |
| Feature gis | 0 | |
| Feature invisible columns | 0 | |
| Feature json | 53.8 M | |
| Feature locale | 1.4 M | |
| Feature subquery | 1.3 M | |
| Feature system versioning | 0 | |
| Feature timezone | 7 | |
| Feature trigger | 0 | |
| Feature window functions | 0 | |
| Feature xml | 0 | |
| Flush commands | 1 | Jumlah perintah FLUSH yang dieksekusi. |
| Handler commit | 45.8 M | Jumlah perintah COMMIT internal. |
| Handler delete | 122.4 k | Berapa kali suatu baris dihapus dari suatu tabel. |
| Handler discover | 7.7 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 | 2.8 G | |
| Handler icp match | 2.8 G | |
| Handler mrr init | 0 | |
| Handler mrr key refills | 0 | |
| Handler mrr rowid refills | 0 | |
| Handler prepare | 0 | |
| Handler read first | 2.4 M | Berapa kali entri pertama dibaca dari suatu indeks. Nilai tinggi menunjukkan bahwa server melakukan banyak pemindaian indeks lengkap; sebagai contoh, SELECT col1 FROM foo, dengan asumsi bahwa col1 diindeks. |
| Handler read key | 192.4 M | Jumlah permintaan membaca suatu baris berdasarkan suatu kunci. Nilai yang tinggi merupakan indikasi bagus bahwa kueri dan tabel Anda diindeks dengan baik. |
| Handler read last | 1 | |
| Handler read next | 8.4 G | Jumlah permintaan membaca baris berikut dalam urutan kunci. Nilai ini bertambah jika Anda melakukan kueri terhadap kolom indeks dengan suatu rentang batasan atau jika Anda melakukan pemindaian indeks. |
| Handler read prev | 91.2 k | Jumlah permintaan membaca baris sebelumnya dalam urutan kunci. Metode baca ini terutama digunakan untuk mengoptimalkan ORDER BY … DESC. |
| Handler read retry | 0 | |
| Handler read rnd | 30.7 M | Jumlah permintaan membaca suatu baris berdasarkan posisi tetap. Nilai ini tinggi jika Anda melakukan banyak kueri yang membutuhkan pengurutan hasil. Anda mungkin memiliki banyak kueri yang mengharuskan MySQL memindai seluruh tabel atau Anda memiliki join yang tidak menggunakan kunci dengan baik. |
| Handler read rnd deleted | 1.2 M | |
| Handler read rnd next | 5.5 G | Jumlah permintaan membaca baris berikut dalam berkas data. Nilai ini tinggi jika Anda melakukan banyak pemindaian tabel. Hal ini secara umum menunjukkan bahwa tabel Anda tidak diindeks dengan baik atau bahwa kueri Anda tidak ditulis dengan memanfaatkan indeks yang Anda miliki. |
| Handler rollback | 669.4 k | Jumlah perintah ROLLBACK internal. |
| Handler savepoint | 0 | |
| Handler savepoint rollback | 0 | |
| Handler tmp delete | 0 | |
| Handler tmp update | 63.3 k | |
| Handler tmp write | 2.9 G | |
| Handler update | 638.6 k | Jumlah permintaan untuk memperbarui baris dalam tabel. |
| Handler write | 1.1 M | Jumlah permintaan untuk menambah baris dalam tabel. |
| Innodb buffer pool dump status | ||
| Innodb buffer pool load status | Buffer pool(s) load completed at 251208 7:30:45 | |
| Innodb buffer pool resize status | ||
| Innodb buffer pool load incomplete | OFF | |
| Innodb buffer pool pages data | 100.5 k | Jumlah halaman yang mengandung data (kotor atau bersih). |
| Innodb buffer pool bytes data | 1.6 G | |
| Innodb buffer pool pages dirty | 26 | Jumlah halaman kotor saat ini. |
| Innodb buffer pool bytes dirty | 426 k | |
| Innodb buffer pool pages flushed | 2.7 M | The number of buffer pool pages that have been requested to be flushed. |
| Innodb buffer pool pages free | 282.2 k | Jumlah halaman bebas. |
| Innodb buffer pool pages misc | 10.6 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 | 393.2 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 | 1.8 k | |
| Innodb buffer pool read ahead evicted | 0 | |
| Innodb buffer pool read requests | 25.8 G | The number of logical read requests InnoDB has done. |
| Innodb buffer pool reads | 97 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 | 7 M | The number writes done to the InnoDB buffer pool. |
| Innodb data fsyncs | 3.6 M | The number of fsync() operations so far. |
| Innodb data pending fsyncs | 0 | Jumlah operasi fsync() tunda saat ini. |
| Innodb data pending reads | 0 | Jumlah baca tunda saat ini. |
| Innodb data pending writes | 0 | Jumlah tulis tunda saat ini. |
| Innodb data read | 1.6 G | Jumlah data yang dibaca sampai saat ini, dalam bita. |
| Innodb data reads | 102.3 k | Jumlah total baca data. |
| Innodb data writes | 5.3 M | Jumlah total tulis data. |
| Innodb data written | 92.5 G | The amount of data written so far, in bytes. |
| Innodb dblwr pages written | 2.7 M | The number of pages that have been written for doublewrite operations. |
| Innodb dblwr writes | 835.3 k | 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 | 3.6 M | The number of log write requests. |
| Innodb log writes | 1.5 M | The number of physical writes to the log file. |
| Innodb os log fsyncs | 1.8 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 | 2.4 G | 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 | 1.2 k | The number of pages created. |
| Innodb pages read | 99.3 k | Jumlah halaman yang dibaca. |
| Innodb pages written | 2.7 M | Jumlah halaman yang ditulis. |
| Innodb row lock current waits | 0 | The number of row locks currently being waited for. |
| Innodb row lock time | 3.1 M | The total time spent in acquiring row locks, in milliseconds. |
| Innodb row lock time avg | 1.9 k | The average time to acquire a row lock, in milliseconds. |
| Innodb row lock time max | 261.5 k | The maximum time to acquire a row lock, in milliseconds. |
| Innodb row lock waits | 1.7 k | The number of times a row lock had to be waited for. |
| Innodb rows deleted | 100.2 k | Jumlah baris yang dihapus dari tabel InnoDB. |
| Innodb rows inserted | 161.1 k | Jumlah baris yang ditambahkan pada tabel InnoDB. |
| Innodb rows read | 11.4 G | Jumlah baris yang dibaca dari tabel InnoDB. |
| Innodb rows updated | 623.2 k | Jumlah baris yang diperbarui pada tabel InnoDB. |
| Innodb system rows deleted | 0 | |
| Innodb system rows inserted | 0 | |
| Innodb system rows read | 1.8 M | |
| Innodb system rows updated | 0 | |
| Innodb num open files | 512 | |
| Innodb truncated status writes | 0 | |
| Innodb available undo logs | 128 | |
| Innodb undo truncations | 0 | |
| Innodb page compression saved | 0 | |
| Innodb num index pages written | 0 | |
| Innodb num non index pages written | 0 | |
| Innodb num pages page compressed | 0 | |
| Innodb num page compressed trim op | 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 have punch hole | ON | |
| Innodb defragment compression failures | 0 | |
| Innodb defragment failures | 0 | |
| Innodb defragment count | 0 | |
| Innodb instant alter column | 0 | |
| Innodb onlineddl rowlog rows | 0 | |
| Innodb onlineddl rowlog pct used | 0 | |
| Innodb onlineddl pct progress | 0 | |
| Innodb secondary index triggered cluster reads | 8.2 G | |
| 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 encryption key rotation list length | 0 | |
| Innodb encryption n merge blocks encrypted | 0 | |
| Innodb encryption n merge blocks decrypted | 0 | |
| Innodb encryption n rowlog blocks encrypted | 0 | |
| Innodb encryption n rowlog blocks decrypted | 0 | |
| Innodb encryption n temp blocks encrypted | 0 | |
| Innodb encryption n temp blocks decrypted | 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 | |
| Innodb scrub log | 0 | |
| Innodb encryption num key requests | 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 | 1.4 M | 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 | 13 | 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 | 98.3 k | The number of requests to read a key block from the cache. |
| Key reads | 1.5 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 | 43.2 k | The number of requests to write a key block to the cache. |
| Key writes | 23.4 k | 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 | 148 | Jumlah maksimum koneksi yang telah digunakan secara bersamaan sejak server dimulai. |
| Memory used | 2 G | |
| Memory used initial | 1.9 G | |
| Not flushed delayed rows | 0 | The number of rows waiting to be written in INSERT DELAYED queues. |
| Open files | 232 | Jumlah file yang terbuka. |
| Open streams | 0 | The number of streams that are open (used mainly for logging). |
| Open table definitions | 563 | |
| Open tables | 2.6 k | Jumlah tabel yang terbuka. |
| Opened files | 45.4 M | |
| Opened plugin libraries | 1.1 k | |
| Opened table definitions | 19 M | |
| Opened tables | 28.2 M | The number of tables that have been opened. If opened tables is big, your table cache value is probably too small. |
| Opened views | 1.2 M | |
| 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 | Jumlah memori kosong untuk cache query. |
| 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 | 125.3 M | |
| Questions | 125.3 M | |
| Rows read | 11.4 G | |
| Rows sent | 489.6 M | |
| Rows tmp read | 2.6 G | |
| Rpl semi sync master clients | 0 | |
| Rpl semi sync master get ack | 0 | |
| Rpl semi sync master net avg wait time | 0 | |
| Rpl semi sync master net wait time | 0 | |
| Rpl semi sync master net waits | 0 | |
| Rpl semi sync master no times | 0 | |
| Rpl semi sync master no tx | 0 | |
| Rpl semi sync master request ack | 0 | |
| Rpl semi sync master status | OFF | |
| Rpl semi sync master timefunc failures | 0 | |
| Rpl semi sync master tx avg wait time | 0 | |
| Rpl semi sync master tx wait time | 0 | |
| Rpl semi sync master tx waits | 0 | |
| Rpl semi sync master wait pos backtraverse | 0 | |
| Rpl semi sync master wait sessions | 0 | |
| Rpl semi sync master yes tx | 0 | |
| Rpl semi sync slave send ack | 0 | |
| Rpl semi sync slave status | OFF | |
| Rpl status | AUTH_MASTER | The status of failsafe replication (not yet implemented). |
| Rpl transactions multi engine | 0 | |
| Select full join | 1.4 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 | 240 | The number of joins that used a range search on a reference table. |
| Select range | 32.6 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 | 66.7 M | 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 | 5 | The number of threads that have taken more than slow_launch_time seconds to create. |
| Slow queries | 178 | 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 | 7.6 k | |
| Sort range | 102.6 k | The number of sorts that were done with ranges. |
| Sort rows | 31.8 M | Jumlah baris diurutkan. |
| Sort scan | 6.9 M | 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 | 298.7 k | |
| Syncs | 21.1 k | |
| Table locks immediate | 4.9 M | The number of times that a table lock was acquired immediately. |
| Table locks waited | 300 | 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 active instances | 5 | |
| Table open cache hits | 67.7 M | |
| Table open cache misses | 105.7 M | |
| Table open cache overflows | 28.2 M | |
| Tc log max pages used | 0 | |
| Tc log page size | 0 | |
| Tc log page waits | 0 | |
| Threadpool idle threads | 0 | |
| Threadpool threads | 0 | |
| Threads cached | 49 | 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 | 2 | Jumlah koneksi yang sedang terbuka. |
| Threads created | 161 | 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 | 6 | The number of threads that are not sleeping. |
| Transactions gtid foreign engine | 0 | |
| Transactions multi engine | 0 | |
| Update scan | 3.4 k | |
| Uptime | 8 hari, 21 jam, 46 menit dan 55 detik | |
| Uptime since flush status | 8 hari, 21 jam, 46 menit dan 55 detik | |
| wsrep | 58.5 T | |
| wsrep applier thread count | 0 | |
| wsrep cluster capabilities | ||
| 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 capabilities | ||
| wsrep provider name | ||
| wsrep provider vendor | ||
| wsrep provider version | ||
| wsrep ready | OFF | |
| wsrep rollbacker thread count | 0 | |
| wsrep thread count | 0 | |
| Key buffer fraction % | 18.59 % | Percentage of used key cache (calculated value) |
| Key write ratio % | 54.17 % | Percentage of physical writes compared to write requests (calculated value) |
| Key read ratio % | 1.48 % | 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) |