Letakkan berkas disini

SQL upload ( 0 ) x-

Server: localhost
Pengaturan Terkait dengan HalamanKlik pada bar untuk menggulir ke atas halaman
Tekan Ctrl+Enter untuk menjalankan kueri Press Enter to execute query
ascending
descending
Order:
Men-Debug SQL
Jumlah
Execution order
Time taken
Order by:
Group queries
Ungroup queries
Tampilkan Buka Show trace Hide trace Jumlah Time taken
Bookmark
Segarkan
Tambah
Tidak ada penanda
Tambah bookmark
Opsi
Kembalikan nilai bawaan





Tampilkan Buka Kueri ulang Ubah Jelaskan Profil Bookmarks Kueri gagal Basis data : Waktu eksekusi kueri :
Filters
VariabelNilaiDeskripsi
Aborted clientsDokumentasi257 257The number of connections that were aborted because the client died without closing the connection properly.
Aborted connectsDokumentasi51 51Jumlah upaya koneksi ke server MySQL yang gagal.
Aborted connects preauthDokumentasi50 50
Access denied errorsDokumentasi1 1
Acl column grantsDokumentasi00
Acl database grantsDokumentasi4 4
Acl function grantsDokumentasi00
Acl procedure grantsDokumentasi00
Acl package spec grantsDokumentasi00
Acl package body grantsDokumentasi00
Acl proxy usersDokumentasi1 1
Acl role grantsDokumentasi00
Acl rolesDokumentasi00
Acl table grantsDokumentasi00
Acl usersDokumentasi7 7
Aria pagecache blocks not flushedDokumentasi00
Aria pagecache blocks unusedDokumentasi15.7 k15694
Aria pagecache blocks usedDokumentasi7.8 k7827
Aria pagecache read requestsDokumentasi59.2 M59237523
Aria pagecache readsDokumentasi5.6 M5627730
Aria pagecache write requestsDokumentasi11.4 M11402065
Aria pagecache writesDokumentasi11.4 M11402050
Aria transaction log syncsDokumentasi7.5 k7478
Binlog commitsDokumentasi00
Binlog group commitsDokumentasi00
Binlog group commit trigger countDokumentasi00
Binlog group commit trigger lock waitDokumentasi00
Binlog group commit trigger timeoutDokumentasi00
Binlog snapshot fileDokumentasi
Binlog snapshot positionDokumentasi00
Binlog bytes writtenDokumentasi00
Binlog cache disk useDokumentasi00Jumlah transaksi yang menggunakan singgahan log biner temporer, namun melebihi nilai binlog_cache_size dan menggunakan berkas temporer untuk menyimpan perintah dari transaksi.
Binlog cache useDokumentasi00Jumlah transaksi yang menggunakan singgahan log biner temporer.
Binlog stmt cache disk useDokumentasi00
Binlog stmt cache useDokumentasi00
Busy timeDokumentasi00.000000
Bytes receivedDokumentasi15.3 G15256028884
Bytes sentDokumentasi39.9 G39874380901
Column compressionsDokumentasi00
Column decompressionsDokumentasi00
Com admin commandsDokumentasi289.6 k289638
Com alter dbDokumentasi00
Com alter db upgradeDokumentasi00
Com alter eventDokumentasi00
Com alter functionDokumentasi00
Com alter procedureDokumentasi00
Com alter serverDokumentasi00
Com alter sequenceDokumentasi00
Com alter tableDokumentasi00
Com alter tablespaceDokumentasi00
Com alter userDokumentasi00
Com analyzeDokumentasi00
Com assign to keycacheDokumentasi00
Com backupDokumentasi00
Com backup lockDokumentasi00
Com beginDokumentasi00
Com binlogDokumentasi00
Com call procedureDokumentasi00
Com change dbDokumentasi7.4 M7375954
Com change masterDokumentasi00
Com checkDokumentasi00
Com checksumDokumentasi00
Com commitDokumentasi4 k3981
Com compound sqlDokumentasi00
Com create dbDokumentasi00
Com create eventDokumentasi00
Com create functionDokumentasi00
Com create indexDokumentasi00
Com create packageDokumentasi00
Com create package bodyDokumentasi00
Com create procedureDokumentasi00
Com create roleDokumentasi00
Com create sequenceDokumentasi00
Com create serverDokumentasi00
Com create tableDokumentasi00
Com create temporary tableDokumentasi00
Com create triggerDokumentasi00
Com create udfDokumentasi00
Com create userDokumentasi00
Com create viewDokumentasi00
Com deleteDokumentasi172.3 k172283
Com delete multiDokumentasi00
Com doDokumentasi00
Com drop dbDokumentasi00
Com drop eventDokumentasi00
Com drop functionDokumentasi00
Com drop indexDokumentasi00
Com drop procedureDokumentasi00
Com drop packageDokumentasi00
Com drop package bodyDokumentasi00
Com drop roleDokumentasi00
Com drop serverDokumentasi00
Com drop sequenceDokumentasi00
Com drop tableDokumentasi00
Com drop temporary tableDokumentasi00
Com drop triggerDokumentasi00
Com drop userDokumentasi00
Com drop viewDokumentasi00
Com empty queryDokumentasi00
Com execute immediateDokumentasi00
Com flushDokumentasi2 2
Com get diagnosticsDokumentasi00
Com grantDokumentasi00
Com grant roleDokumentasi00
Com ha closeDokumentasi00
Com ha openDokumentasi00
Com ha readDokumentasi00
Com helpDokumentasi00
Com insertDokumentasi552.7 k552728
Com insert selectDokumentasi00
Com install pluginDokumentasi00
Com killDokumentasi00
Com loadDokumentasi00
Com lock tablesDokumentasi9 9
Com multiDokumentasi00
Com optimizeDokumentasi00
Com preload keysDokumentasi00
Com purgeDokumentasi00
Com purge before dateDokumentasi00
Com release savepointDokumentasi00
Com rename tableDokumentasi00
Com rename userDokumentasi00
Com repairDokumentasi00
Com replaceDokumentasi239.6 k239571
Com replace selectDokumentasi00
Com resetDokumentasi00
Com resignalDokumentasi00
Com revokeDokumentasi00
Com revoke allDokumentasi00
Com revoke roleDokumentasi00
Com rollbackDokumentasi7 7
Com rollback to savepointDokumentasi00
Com savepointDokumentasi00
Com selectDokumentasi101.1 M101113057
Com set optionDokumentasi4.2 M4175259
Com show authorsDokumentasi00
Com show binlog eventsDokumentasi00
Com show binlogsDokumentasi905 905
Com show charsetsDokumentasi00
Com show collationsDokumentasi00
Com show contributorsDokumentasi00
Com show create dbDokumentasi00
Com show create eventDokumentasi00
Com show create funcDokumentasi00
Com show create packageDokumentasi00
Com show create package bodyDokumentasi00
Com show create procDokumentasi20 20
Com show create tableDokumentasi1.4 M1369707
Com show create triggerDokumentasi00
Com show create userDokumentasi00
Com show databasesDokumentasi00
Com show engine logsDokumentasi00
Com show engine mutexDokumentasi00
Com show engine statusDokumentasi1 1
Com show errorsDokumentasi00
Com show eventsDokumentasi00
Com show explainDokumentasi00
Com show fieldsDokumentasi5.5 M5458164
Com show function statusDokumentasi00
Com show genericDokumentasi00
Com show grantsDokumentasi1.3 M1349213
Com show keysDokumentasi6.7 M6684423
Com show master statusDokumentasi293 293
Com show open tablesDokumentasi00
Com show package statusDokumentasi00
Com show package body statusDokumentasi00
Com show pluginsDokumentasi00
Com show privilegesDokumentasi00
Com show procedure statusDokumentasi00
Com show processlistDokumentasi6 6
Com show profileDokumentasi00
Com show profilesDokumentasi00
Com show relaylog eventsDokumentasi00
Com show slave hostsDokumentasi00
Com show slave statusDokumentasi303 303
Com show statusDokumentasi45 45
Com show storage enginesDokumentasi2.3 k2299
Com show table statusDokumentasi3.5 k3510
Com show tablesDokumentasi1.4 M1404475
Com show triggersDokumentasi00
Com show variablesDokumentasi2.6 M2639850
Com show warningsDokumentasi1.3 M1314813
Com shutdownDokumentasi00
Com signalDokumentasi00
Com start all slavesDokumentasi00
Com start slaveDokumentasi00
Com stmt closeDokumentasi00
Com stmt executeDokumentasi00
Com stmt fetchDokumentasi00
Com stmt prepareDokumentasi00
Com stmt reprepareDokumentasi00
Com stmt resetDokumentasi00
Com stmt send long dataDokumentasi00
Com stop all slavesDokumentasi00
Com stop slaveDokumentasi00
Com truncateDokumentasi00
Com uninstall pluginDokumentasi00
Com unlock tablesDokumentasi9 9
Com updateDokumentasi18.7 k18665
Com update multiDokumentasi00
Com xa commitDokumentasi00
Com xa endDokumentasi00
Com xa prepareDokumentasi00
Com xa recoverDokumentasi00
Com xa rollbackDokumentasi00
Com xa startDokumentasi00
CompressionDokumentasiOFFOFF
Connection errors acceptDokumentasi00
Connection errors internalDokumentasi00
Connection errors max connectionsDokumentasi00
Connection errors peer addressDokumentasi00
Connection errors selectDokumentasi00
Connection errors tcpwrapDokumentasi00
ConnectionsDokumentasi7.4 M7386684Jumlah upaya koneksi ke server MySQL (baik berhasil maupun tidak).
Cpu timeDokumentasi00.000000
Created tmp disk tablesDokumentasi5.6 M5628567Jumlah 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 filesDokumentasi6 6Jumlah berkas temporer yang telah dibuat mysqld.
Created tmp tablesDokumentasi95 M94963971Jumlah tabel temporer dalam-memori yang dibuat otomatis oleh server sewaktu mengeksekusi perintah.
Delayed errorsDokumentasi00Jumlah baris yang ditulis oleh INSERT DELAYED yang menyebabkan beberapa galat (kemungkinan karena kunci duplikat).
Delayed insert threadsDokumentasi00Jumlah thread handler INSERT DELAYED yang dipakai. Setiap tabel berbeda yang menggunakan INSERT DELAYED mendapat satu thread sendiri.
Delayed writesDokumentasi00Jumlah baris INSERT DELAYED yang ditulis.
Delete scanDokumentasi2 k1985
Empty queriesDokumentasi48.6 M48626620
Executed eventsDokumentasi00
Executed triggersDokumentasi00
Feature application time periodsDokumentasi00
Feature check constraintDokumentasi3.2 k3187
Feature custom aggregate functionsDokumentasi00
Feature delay key writeDokumentasi00
Feature dynamic columnsDokumentasi00
Feature fulltextDokumentasi00
Feature gisDokumentasi00
Feature invisible columnsDokumentasi00
Feature jsonDokumentasi60.9 M60878537
Feature localeDokumentasi1.4 M1372085
Feature subqueryDokumentasi1.5 M1462289
Feature system versioningDokumentasi00
Feature timezoneDokumentasi9 9
Feature triggerDokumentasi00
Feature window functionsDokumentasi00
Feature xmlDokumentasi00
Flush commandsDokumentasi1 1Jumlah perintah FLUSH yang dieksekusi.
Handler commitDokumentasi49.8 M49774483Jumlah perintah COMMIT internal.
Handler deleteDokumentasi182.3 k182267Berapa kali suatu baris dihapus dari suatu tabel.
Handler discoverDokumentasi6.2 k6197The 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 lockDokumentasi00
Handler icp attemptsDokumentasi2.8 G2839064872
Handler icp matchDokumentasi2.8 G2838894868
Handler mrr initDokumentasi00
Handler mrr key refillsDokumentasi00
Handler mrr rowid refillsDokumentasi00
Handler prepareDokumentasi00
Handler read firstDokumentasi2.3 M2262324Berapa 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 keyDokumentasi185.3 M185348378Jumlah permintaan membaca suatu baris berdasarkan suatu kunci. Nilai yang tinggi merupakan indikasi bagus bahwa kueri dan tabel Anda diindeks dengan baik.
Handler read lastDokumentasi00
Handler read nextDokumentasi9.6 G9582506544Jumlah 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 prevDokumentasi186 186Jumlah permintaan membaca baris sebelumnya dalam urutan kunci. Metode baca ini terutama digunakan untuk mengoptimalkan ORDER BY … DESC.
Handler read retryDokumentasi00
Handler read rndDokumentasi31.1 M31079228Jumlah 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 deletedDokumentasi1.4 M1351105
Handler read rnd nextDokumentasi5.8 G5792913909Jumlah 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 rollbackDokumentasi713.3 k713300Jumlah perintah ROLLBACK internal.
Handler savepointDokumentasi00
Handler savepoint rollbackDokumentasi00
Handler tmp deleteDokumentasi00
Handler tmp updateDokumentasi11.4 k11374
Handler tmp writeDokumentasi3.1 G3141709193
Handler updateDokumentasi255.8 k255814Jumlah permintaan untuk memperbarui baris dalam tabel.
Handler writeDokumentasi792.3 k792250Jumlah permintaan untuk menambah baris dalam tabel.
Innodb buffer pool dump statusDokumentasi
Innodb buffer pool load statusDokumentasiBuffer pool(s) load completed at 251127 9:48:25Buffer pool(s) load completed at 251127 9:48:25
Innodb buffer pool resize statusDokumentasi
Innodb buffer pool load incompleteDokumentasiOFFOFF
Innodb buffer pool pages dataDokumentasi98.8 k98838Jumlah halaman yang mengandung data (kotor atau bersih).
Innodb buffer pool bytes dataDokumentasi1.6 G1619361792
Innodb buffer pool pages dirtyDokumentasi53 53Jumlah halaman kotor saat ini.
Innodb buffer pool bytes dirtyDokumentasi868.4 k868352
Innodb buffer pool pages flushedDokumentasi1.6 M1587256The number of buffer pool pages that have been requested to be flushed.
Innodb buffer pool pages freeDokumentasi284.1 k284061Jumlah halaman bebas.
Innodb buffer pool pages miscDokumentasi10.3 k10317The 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 totalDokumentasi393.2 k393216Total size of buffer pool, in pages.
Innodb buffer pool read ahead rndDokumentasi00The 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 aheadDokumentasi828 828
Innodb buffer pool read ahead evictedDokumentasi00
Innodb buffer pool read requestsDokumentasi29.6 G29596291557The number of logical read requests InnoDB has done.
Innodb buffer pool readsDokumentasi96.4 k96392The number of logical reads that InnoDB could not satisfy from buffer pool and had to do a single-page read.
Innodb buffer pool wait freeDokumentasi00Normally, 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 requestsDokumentasi4.9 M4935185The number writes done to the InnoDB buffer pool.
Innodb data fsyncsDokumentasi2.3 M2317502The number of fsync() operations so far.
Innodb data pending fsyncsDokumentasi00Jumlah operasi fsync() tunda saat ini.
Innodb data pending readsDokumentasi00Jumlah baca tunda saat ini.
Innodb data pending writesDokumentasi00Jumlah tulis tunda saat ini.
Innodb data readDokumentasi1.6 G1599851008Jumlah data yang dibaca sampai saat ini, dalam bita.
Innodb data readsDokumentasi100.7 k100677Jumlah total baca data.
Innodb data writesDokumentasi3.2 M3238308Jumlah total tulis data.
Innodb data writtenDokumentasi53.4 G53437808128The amount of data written so far, in bytes.
Innodb dblwr pages writtenDokumentasi1.6 M1587125The number of pages that have been written for doublewrite operations.
Innodb dblwr writesDokumentasi515.8 k515789The number of doublewrite operations that have been performed.
Innodb log waitsDokumentasi00The 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 requestsDokumentasi1.7 M1728237The number of log write requests.
Innodb log writesDokumentasi974.7 k974650The number of physical writes to the log file.
Innodb os log fsyncsDokumentasi1.1 M1135267The number of fsync() writes done to the log file.
Innodb os log pending fsyncsDokumentasi00The number of pending log file fsyncs.
Innodb os log pending writesDokumentasi00Pending log file writes.
Innodb os log writtenDokumentasi1.3 G1346547200The number of bytes written to the log file.
Innodb page sizeDokumentasi16.4 k16384The 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 createdDokumentasi1.2 k1225The number of pages created.
Innodb pages readDokumentasi97.6 k97613Jumlah halaman yang dibaca.
Innodb pages writtenDokumentasi1.6 M1587256Jumlah halaman yang ditulis.
Innodb row lock current waitsDokumentasi00The number of row locks currently being waited for.
Innodb row lock timeDokumentasi122 122The total time spent in acquiring row locks, in milliseconds.
Innodb row lock time avgDokumentasi00The average time to acquire a row lock, in milliseconds.
Innodb row lock time maxDokumentasi72 72The maximum time to acquire a row lock, in milliseconds.
Innodb row lock waitsDokumentasi756 756The number of times a row lock had to be waited for.
Innodb rows deletedDokumentasi159.7 k159665Jumlah baris yang dihapus dari tabel InnoDB.
Innodb rows insertedDokumentasi223.3 k223322Jumlah baris yang ditambahkan pada tabel InnoDB.
Innodb rows readDokumentasi12.7 G12731592058Jumlah baris yang dibaca dari tabel InnoDB.
Innodb rows updatedDokumentasi247.6 k247616Jumlah baris yang diperbarui pada tabel InnoDB.
Innodb system rows deletedDokumentasi00
Innodb system rows insertedDokumentasi00
Innodb system rows readDokumentasi1.9 M1926594
Innodb system rows updatedDokumentasi00
Innodb num open filesDokumentasi512 512
Innodb truncated status writesDokumentasi00
Innodb available undo logsDokumentasi128 128
Innodb undo truncationsDokumentasi00
Innodb page compression savedDokumentasi00
Innodb num index pages writtenDokumentasi00
Innodb num non index pages writtenDokumentasi00
Innodb num pages page compressedDokumentasi00
Innodb num page compressed trim opDokumentasi00
Innodb num pages page decompressedDokumentasi00
Innodb num pages page compression errorDokumentasi00
Innodb num pages encryptedDokumentasi00
Innodb num pages decryptedDokumentasi00
Innodb have lz4DokumentasiOFFOFF
Innodb have lzoDokumentasiOFFOFF
Innodb have lzmaDokumentasiOFFOFF
Innodb have bzip2DokumentasiONON
Innodb have snappyDokumentasiOFFOFF
Innodb have punch holeDokumentasiONON
Innodb defragment compression failuresDokumentasi00
Innodb defragment failuresDokumentasi00
Innodb defragment countDokumentasi00
Innodb instant alter columnDokumentasi00
Innodb onlineddl rowlog rowsDokumentasi00
Innodb onlineddl rowlog pct usedDokumentasi00
Innodb onlineddl pct progressDokumentasi00
Innodb secondary index triggered cluster readsDokumentasi9.5 G9524719790
Innodb secondary index triggered cluster reads avoidedDokumentasi00
Innodb encryption rotation pages read from cacheDokumentasi00
Innodb encryption rotation pages read from diskDokumentasi00
Innodb encryption rotation pages modifiedDokumentasi00
Innodb encryption rotation pages flushedDokumentasi00
Innodb encryption rotation estimated iopsDokumentasi00
Innodb encryption key rotation list lengthDokumentasi00
Innodb encryption n merge blocks encryptedDokumentasi00
Innodb encryption n merge blocks decryptedDokumentasi00
Innodb encryption n rowlog blocks encryptedDokumentasi00
Innodb encryption n rowlog blocks decryptedDokumentasi00
Innodb encryption n temp blocks encryptedDokumentasi00
Innodb encryption n temp blocks decryptedDokumentasi00
Innodb scrub background page reorganizationsDokumentasi00
Innodb scrub background page splitsDokumentasi00
Innodb scrub background page split failures underflowDokumentasi00
Innodb scrub background page split failures out of filespaceDokumentasi00
Innodb scrub background page split failures missing indexDokumentasi00
Innodb scrub background page split failures unknownDokumentasi00
Innodb scrub logDokumentasi00
Innodb encryption num key requestsDokumentasi00
Key blocks not flushedDokumentasi00The 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 unusedDokumentasi1.4 M1365533The 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 usedDokumentasi9 9The 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 warmDokumentasi00
Key read requestsDokumentasi98.9 k98917The number of requests to read a key block from the cache.
Key readsDokumentasi3.6 k3625The 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 requestsDokumentasi43.6 k43603The number of requests to write a key block to the cache.
Key writesDokumentasi23.6 k23602The number of physical writes of a key block to disk.
Last query costDokumentasi00.000000The 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 countDokumentasi00
Master gtid wait timeDokumentasi00
Master gtid wait timeoutsDokumentasi00
Max statement time exceededDokumentasi00
Max used connectionsDokumentasi45 45Jumlah maksimum koneksi yang telah digunakan secara bersamaan sejak server dimulai.
Memory usedDokumentasi2 G1958336936
Memory used initialDokumentasi1.9 G1857212624
Not flushed delayed rowsDokumentasi00The number of rows waiting to be written in INSERT DELAYED queues.
Open filesDokumentasi56 56Jumlah file yang terbuka.
Open streamsDokumentasi00The number of streams that are open (used mainly for logging).
Open table definitionsDokumentasi482 482
Open tablesDokumentasi512 512Jumlah tabel yang terbuka.
Opened filesDokumentasi31 M30974238
Opened plugin librariesDokumentasi312 312
Opened table definitionsDokumentasi5 M5009420
Opened tablesDokumentasi4.7 M4748540The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
Opened viewsDokumentasi1.4 M1352742
Performance schema accounts lostDokumentasi00
Performance schema cond classes lostDokumentasi00
Performance schema cond instances lostDokumentasi00
Performance schema digest lostDokumentasi00
Performance schema file classes lostDokumentasi00
Performance schema file handles lostDokumentasi00
Performance schema file instances lostDokumentasi00
Performance schema hosts lostDokumentasi00
Performance schema locker lostDokumentasi00
Performance schema mutex classes lostDokumentasi00
Performance schema mutex instances lostDokumentasi00
Performance schema rwlock classes lostDokumentasi00
Performance schema rwlock instances lostDokumentasi00
Performance schema session connect attrs lostDokumentasi00
Performance schema socket classes lostDokumentasi00
Performance schema socket instances lostDokumentasi00
Performance schema stage classes lostDokumentasi00
Performance schema statement classes lostDokumentasi00
Performance schema table handles lostDokumentasi00
Performance schema table instances lostDokumentasi00
Performance schema thread classes lostDokumentasi00
Performance schema thread instances lostDokumentasi00
Performance schema users lostDokumentasi00
Prepared stmt countDokumentasi00
Qcache free blocksDokumentasi1 1The 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 memoryDokumentasi1 M1031320Jumlah memori kosong untuk cache query.
Qcache hitsDokumentasi00The number of cache hits.
Qcache insertsDokumentasi00The number of queries added to the cache.
Qcache lowmem prunesDokumentasi00The 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 cachedDokumentasi00The number of non-cached queries (not cachable, or not cached due to the query_cache_type setting).
Qcache queries in cacheDokumentasi00The number of queries registered in the cache.
Qcache total blocksDokumentasi1 1The total number of blocks in the query cache.
QueriesDokumentasi141.3 M141268030
QuestionsDokumentasi141.3 M141268030
Rows readDokumentasi12.7 G12745116131
Rows sentDokumentasi258.2 M258199726
Rows tmp readDokumentasi2.7 G2733978957
Rpl semi sync master clientsDokumentasi00
Rpl semi sync master get ackDokumentasi00
Rpl semi sync master net avg wait timeDokumentasi00
Rpl semi sync master net wait timeDokumentasi00
Rpl semi sync master net waitsDokumentasi00
Rpl semi sync master no timesDokumentasi00
Rpl semi sync master no txDokumentasi00
Rpl semi sync master request ackDokumentasi00
Rpl semi sync master statusDokumentasiOFFOFF
Rpl semi sync master timefunc failuresDokumentasi00
Rpl semi sync master tx avg wait timeDokumentasi00
Rpl semi sync master tx wait timeDokumentasi00
Rpl semi sync master tx waitsDokumentasi00
Rpl semi sync master wait pos backtraverseDokumentasi00
Rpl semi sync master wait sessionsDokumentasi00
Rpl semi sync master yes txDokumentasi00
Rpl semi sync slave send ackDokumentasi00
Rpl semi sync slave statusDokumentasiOFFOFF
Rpl statusDokumentasiAUTH_MASTERAUTH_MASTERThe status of failsafe replication (not yet implemented).
Rpl transactions multi engineDokumentasi00
Select full joinDokumentasi1.4 M1412787The 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 joinDokumentasi258 258The number of joins that used a range search on a reference table.
Select rangeDokumentasi44.2 k44175The number of joins that used ranges on the first table. (It's normally not critical even if this is big.)
Select range checkDokumentasi00The 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 scanDokumentasi77.4 M77353107The number of joins that did a full scan of the first table.
Slave connectionsDokumentasi00
Slave heartbeat periodDokumentasi00.000
Slave open temp tablesDokumentasi00The number of temporary tables currently open by the slave SQL thread.
Slave received heartbeatsDokumentasi00
Slave retried transactionsDokumentasi00Total (since startup) number of times the replication slave SQL thread has retried transactions.
Slave runningDokumentasiOFFOFFThis is ON if this server is a slave that is connected to a master.
Slave skipped errorsDokumentasi00
Slaves connectedDokumentasi00
Slaves runningDokumentasi00
Slow launch threadsDokumentasi00The number of threads that have taken more than slow_launch_time seconds to create.
Slow queriesDokumentasi10 10The number of queries that have taken more than long_query_time seconds.Dokumentasi
Sort merge passesDokumentasi1 1The 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 sortsDokumentasi7.6 k7623
Sort rangeDokumentasi108.5 k108519The number of sorts that were done with ranges.
Sort rowsDokumentasi31.8 M31777268Jumlah baris diurutkan.
Sort scanDokumentasi6.6 M6577673The number of sorts that were done by scanning the table.
Ssl accept renegotiatesDokumentasi00
Ssl acceptsDokumentasi00
Ssl callback cache hitsDokumentasi00
Ssl cipherDokumentasi
Ssl cipher listDokumentasi
Ssl client connectsDokumentasi00
Ssl connect renegotiatesDokumentasi00
Ssl ctx verify depthDokumentasi00
Ssl ctx verify modeDokumentasi00
Ssl default timeoutDokumentasi00
Ssl finished acceptsDokumentasi00
Ssl finished connectsDokumentasi00
Ssl server not afterDokumentasi
Ssl server not beforeDokumentasi
Ssl session cache hitsDokumentasi00
Ssl session cache missesDokumentasi00
Ssl session cache modeDokumentasiNONENONE
Ssl session cache overflowsDokumentasi00
Ssl session cache sizeDokumentasi00
Ssl session cache timeoutsDokumentasi00
Ssl sessions reusedDokumentasi00
Ssl used session cache entriesDokumentasi00
Ssl verify depthDokumentasi00
Ssl verify modeDokumentasi00
Ssl versionDokumentasi
Subquery cache hitDokumentasi00
Subquery cache missDokumentasi325.1 k325074
SyncsDokumentasi29.3 k29253
Table locks immediateDokumentasi4.8 M4823017The number of times that a table lock was acquired immediately.
Table locks waitedDokumentasi314 314The 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 instancesDokumentasi1 1
Table open cache hitsDokumentasi71.7 M71684696
Table open cache missesDokumentasi8.2 M8150626
Table open cache overflowsDokumentasi4.6 M4580352
Tc log max pages usedDokumentasi00
Tc log page sizeDokumentasi00
Tc log page waitsDokumentasi00
Threadpool idle threadsDokumentasi00
Threadpool threadsDokumentasi00
Threads cachedDokumentasi31 31The 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 connectedDokumentasi14 14Jumlah koneksi yang sedang terbuka.
Threads createdDokumentasi85 85The 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 runningDokumentasi6 6The number of threads that are not sleeping.
Transactions gtid foreign engineDokumentasi00
Transactions multi engineDokumentasi00
Update scanDokumentasi3.7 k3718
UptimeDokumentasi9 hari, 4 jam, 36 menit dan 58 detik794218
Uptime since flush statusDokumentasi9 hari, 4 jam, 36 menit dan 58 detik794218
wsrepDokumentasi61.8 T61783946836279
wsrep applier thread countDokumentasi00
wsrep cluster capabilitiesDokumentasi
wsrep cluster conf idDokumentasi18.4 E18446744073709551615
wsrep cluster sizeDokumentasi00
wsrep cluster state uuidDokumentasi
wsrep cluster statusDokumentasiDisconnectedDisconnected
wsrep connectedDokumentasiOFFOFF
wsrep local bf abortsDokumentasi00
wsrep local indexDokumentasi18.4 E18446744073709551615
wsrep provider capabilitiesDokumentasi
wsrep provider nameDokumentasi
wsrep provider vendorDokumentasi
wsrep provider versionDokumentasi
wsrep readyDokumentasiOFFOFF
wsrep rollbacker thread countDokumentasi00
wsrep thread countDokumentasi00
Key buffer fraction %18.59 %18.588014632937Percentage of used key cache (calculated value)
Key write ratio %54.13 %54.129303029608Percentage of physical writes compared to write requests (calculated value)
Key read ratio %3.66 %3.6646885772921Key cache miss calculated as rate of physical reads compared to read requests (calculated value)
Threads cache hitrate %100.00 %99.998849280679Thread cache hit rate (calculated value)