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 clientsDokumentasi155 155The number of connections that were aborted because the client died without closing the connection properly.
Aborted connectsDokumentasi50 50Jumlah upaya koneksi ke server MySQL yang gagal.
Aborted connects preauthDokumentasi50 50
Access denied errorsDokumentasi00
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 k15703
Aria pagecache blocks usedDokumentasi7.8 k7848
Aria pagecache read requestsDokumentasi7.9 M7883901
Aria pagecache readsDokumentasi354.3 k354312
Aria pagecache write requestsDokumentasi781 k780979
Aria pagecache writesDokumentasi781 k780965
Aria transaction log syncsDokumentasi503 503
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 receivedDokumentasi2.9 G2915408919
Bytes sentDokumentasi8.6 G8555662756
Column compressionsDokumentasi00
Column decompressionsDokumentasi00
Com admin commandsDokumentasi64.5 k64459
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 dbDokumentasi4.2 M4176133
Com change masterDokumentasi00
Com checkDokumentasi00
Com checksumDokumentasi00
Com commitDokumentasi3.1 k3085
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 deleteDokumentasi85.3 k85292
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 flushDokumentasi3 3
Com get diagnosticsDokumentasi00
Com grantDokumentasi00
Com grant roleDokumentasi00
Com ha closeDokumentasi00
Com ha openDokumentasi00
Com ha readDokumentasi00
Com helpDokumentasi00
Com insertDokumentasi220 k220031
Com insert selectDokumentasi00
Com install pluginDokumentasi00
Com killDokumentasi00
Com loadDokumentasi00
Com lock tablesDokumentasi2 2
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 replaceDokumentasi67.9 k67889
Com replace selectDokumentasi00
Com resetDokumentasi00
Com resignalDokumentasi00
Com revokeDokumentasi00
Com revoke allDokumentasi00
Com revoke roleDokumentasi00
Com rollbackDokumentasi12 12
Com rollback to savepointDokumentasi00
Com savepointDokumentasi00
Com selectDokumentasi9.8 M9770772
Com set optionDokumentasi248 k248001
Com show authorsDokumentasi00
Com show binlog eventsDokumentasi00
Com show binlogsDokumentasi1.6 k1592
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 procDokumentasi4 4
Com show create tableDokumentasi62.5 k62494
Com show create triggerDokumentasi00
Com show create userDokumentasi00
Com show databasesDokumentasi00
Com show engine logsDokumentasi00
Com show engine mutexDokumentasi00
Com show engine statusDokumentasi00
Com show errorsDokumentasi00
Com show eventsDokumentasi00
Com show explainDokumentasi00
Com show fieldsDokumentasi267.1 k267123
Com show function statusDokumentasi00
Com show genericDokumentasi00
Com show grantsDokumentasi69.6 k69636
Com show keysDokumentasi150.1 k150143
Com show master statusDokumentasi238 238
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 processlistDokumentasi4 4
Com show profileDokumentasi00
Com show profilesDokumentasi00
Com show relaylog eventsDokumentasi00
Com show slave hostsDokumentasi00
Com show slave statusDokumentasi243 243
Com show statusDokumentasi27 27
Com show storage enginesDokumentasi3.1 k3089
Com show table statusDokumentasi9.3 k9347
Com show tablesDokumentasi167.3 k167262
Com show triggersDokumentasi00
Com show variablesDokumentasi52.4 k52364
Com show warningsDokumentasi19 k18959
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 tablesDokumentasi00
Com updateDokumentasi14.1 k14108
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
ConnectionsDokumentasi4.2 M4181690Jumlah upaya koneksi ke server MySQL (baik berhasil maupun tidak).
Cpu timeDokumentasi00.000000
Created tmp disk tablesDokumentasi351.4 k351383Jumlah 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 tablesDokumentasi3.6 M3606141Jumlah 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 scanDokumentasi1.4 k1397
Empty queriesDokumentasi3.2 M3232081
Executed eventsDokumentasi00
Executed triggersDokumentasi00
Feature application time periodsDokumentasi00
Feature check constraintDokumentasi4.9 k4864
Feature custom aggregate functionsDokumentasi00
Feature delay key writeDokumentasi00
Feature dynamic columnsDokumentasi00
Feature fulltextDokumentasi00
Feature gisDokumentasi00
Feature invisible columnsDokumentasi00
Feature jsonDokumentasi3.3 M3250658
Feature localeDokumentasi80.1 k80105
Feature subqueryDokumentasi224.7 k224720
Feature system versioningDokumentasi00
Feature timezoneDokumentasi2 2
Feature triggerDokumentasi00
Feature window functionsDokumentasi00
Feature xmlDokumentasi00
Flush commandsDokumentasi1 1Jumlah perintah FLUSH yang dieksekusi.
Handler commitDokumentasi8 M8007285Jumlah perintah COMMIT internal.
Handler deleteDokumentasi93 k92968Berapa kali suatu baris dihapus dari suatu tabel.
Handler discoverDokumentasi2.3 k2307The 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 attemptsDokumentasi3.3 G3264834379
Handler icp matchDokumentasi3.3 G3264535873
Handler mrr initDokumentasi00
Handler mrr key refillsDokumentasi00
Handler mrr rowid refillsDokumentasi00
Handler prepareDokumentasi00
Handler read firstDokumentasi836.3 k836291Berapa 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 keyDokumentasi226.4 M226360943Jumlah permintaan membaca suatu baris berdasarkan suatu kunci. Nilai yang tinggi merupakan indikasi bagus bahwa kueri dan tabel Anda diindeks dengan baik.
Handler read lastDokumentasi2 2
Handler read nextDokumentasi13.7 G13665777882Jumlah 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 prevDokumentasi454 454Jumlah permintaan membaca baris sebelumnya dalam urutan kunci. Metode baca ini terutama digunakan untuk mengoptimalkan ORDER BY … DESC.
Handler read retryDokumentasi00
Handler read rndDokumentasi7.2 M7164870Jumlah 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 deletedDokumentasi70.7 k70718
Handler read rnd nextDokumentasi3.6 G3622566192Jumlah 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 rollbackDokumentasi375.6 k375586Jumlah perintah ROLLBACK internal.
Handler savepointDokumentasi00
Handler savepoint rollbackDokumentasi00
Handler tmp deleteDokumentasi00
Handler tmp updateDokumentasi17.2 k17186
Handler tmp writeDokumentasi146.1 M146095107
Handler updateDokumentasi80.2 k80210Jumlah permintaan untuk memperbarui baris dalam tabel.
Handler writeDokumentasi287.9 k287919Jumlah permintaan untuk menambah baris dalam tabel.
Innodb buffer pool dump statusDokumentasi
Innodb buffer pool load statusDokumentasiBuffer pool(s) load completed at 260926 8:10:27Buffer pool(s) load completed at 260926 8:10:27
Innodb buffer pool resize statusDokumentasi
Innodb buffer pool load incompleteDokumentasiOFFOFF
Innodb buffer pool pages dataDokumentasi103.7 k103730Jumlah halaman yang mengandung data (kotor atau bersih).
Innodb buffer pool bytes dataDokumentasi1.7 G1699512320
Innodb buffer pool pages dirtyDokumentasi29 29Jumlah halaman kotor saat ini.
Innodb buffer pool bytes dirtyDokumentasi475.1 k475136
Innodb buffer pool pages flushedDokumentasi907.9 k907882The number of buffer pool pages that have been requested to be flushed.
Innodb buffer pool pages freeDokumentasi279.2 k279180Jumlah halaman bebas.
Innodb buffer pool pages miscDokumentasi10.3 k10306The 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 aheadDokumentasi749 749
Innodb buffer pool read ahead evictedDokumentasi00
Innodb buffer pool read requestsDokumentasi41.8 G41797925109The number of logical read requests InnoDB has done.
Innodb buffer pool readsDokumentasi100.9 k100851The 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 requestsDokumentasi2.2 M2246363The number writes done to the InnoDB buffer pool.
Innodb data fsyncsDokumentasi1.2 M1246295The 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.7 G1681082880Jumlah data yang dibaca sampai saat ini, dalam bita.
Innodb data readsDokumentasi105.6 k105639Jumlah total baca data.
Innodb data writesDokumentasi1.8 M1777916Jumlah total tulis data.
Innodb data writtenDokumentasi30.4 G30364033024The amount of data written so far, in bytes.
Innodb dblwr pages writtenDokumentasi907.8 k907751The number of pages that have been written for doublewrite operations.
Innodb dblwr writesDokumentasi280.5 k280470The 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 requestsDokumentasi526.5 k526531The number of log write requests.
Innodb log writesDokumentasi471.9 k471877The number of physical writes to the log file.
Innodb os log fsyncsDokumentasi589.6 k589566The 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 writtenDokumentasi556.5 M556461568The 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.1 k1130The number of pages created.
Innodb pages readDokumentasi102.6 k102600Jumlah halaman yang dibaca.
Innodb pages writtenDokumentasi907.9 k907882Jumlah halaman yang ditulis.
Innodb row lock current waitsDokumentasi00The number of row locks currently being waited for.
Innodb row lock timeDokumentasi00The 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 maxDokumentasi00The maximum time to acquire a row lock, in milliseconds.
Innodb row lock waitsDokumentasi4 4The number of times a row lock had to be waited for.
Innodb rows deletedDokumentasi75.4 k75447Jumlah baris yang dihapus dari tabel InnoDB.
Innodb rows insertedDokumentasi124.6 k124582Jumlah baris yang ditambahkan pada tabel InnoDB.
Innodb rows readDokumentasi17.3 G17320029300Jumlah baris yang dibaca dari tabel InnoDB.
Innodb rows updatedDokumentasi77.8 k77761Jumlah baris yang diperbarui pada tabel InnoDB.
Innodb system rows deletedDokumentasi00
Innodb system rows insertedDokumentasi00
Innodb system rows readDokumentasi494.2 k494156
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 readsDokumentasi13.5 G13536315107
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 usedDokumentasi8 8The 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 requestsDokumentasi76.8 k76750The number of requests to read a key block from the cache.
Key readsDokumentasi2.4 k2431The 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 requestsDokumentasi34 k34029The number of requests to write a key block to the cache.
Key writesDokumentasi18.4 k18430The 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 connectionsDokumentasi44 44Jumlah maksimum koneksi yang telah digunakan secara bersamaan sejak server dimulai.
Memory usedDokumentasi1.9 G1949737040
Memory used initialDokumentasi1.9 G1857212624
Not flushed delayed rowsDokumentasi00The number of rows waiting to be written in INSERT DELAYED queues.
Open filesDokumentasi131 131Jumlah file yang terbuka.
Open streamsDokumentasi00The number of streams that are open (used mainly for logging).
Open table definitionsDokumentasi503 503
Open tablesDokumentasi512 512Jumlah tabel yang terbuka.
Opened filesDokumentasi15.1 M15060665
Opened plugin librariesDokumentasi273 273
Opened table definitionsDokumentasi12.1 M12127319
Opened tablesDokumentasi11 M11038382The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
Opened viewsDokumentasi72.1 k72127
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.
QueriesDokumentasi19.6 M19573175
QuestionsDokumentasi19.6 M19573175
Rows readDokumentasi17.3 G17328010840
Rows sentDokumentasi110.5 M110460200
Rows tmp readDokumentasi147.1 M147058429
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 joinDokumentasi119.4 k119425The 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 joinDokumentasi00The number of joins that used a range search on a reference table.
Select rangeDokumentasi42.5 k42451The 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 scanDokumentasi4 M4048183The 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 queriesDokumentasi00The 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 sortsDokumentasi5.2 k5209
Sort rangeDokumentasi26.5 k26498The number of sorts that were done with ranges.
Sort rowsDokumentasi7.8 M7815377Jumlah baris diurutkan.
Sort scanDokumentasi1.2 M1185344The 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 missDokumentasi294.3 k294294
SyncsDokumentasi14.4 k14433
Table locks immediateDokumentasi2.9 M2869032The number of times that a table lock was acquired immediately.
Table locks waitedDokumentasi204 204The 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 hitsDokumentasi20.8 M20822054
Table open cache missesDokumentasi11.5 M11545989
Table open cache overflowsDokumentasi11 M11036680
Tc log max pages usedDokumentasi00
Tc log page sizeDokumentasi00
Tc log page waitsDokumentasi00
Threadpool idle threadsDokumentasi00
Threadpool threadsDokumentasi00
Threads cachedDokumentasi30 30The 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 createdDokumentasi217 217The 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 scanDokumentasi2.7 k2666
UptimeDokumentasi6 hari, 6 jam, 9 menit dan 32 detik540572
Uptime since flush statusDokumentasi6 hari, 6 jam, 9 menit dan 32 detik540572
wsrepDokumentasi55.2 T55212696941621
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.16 %54.159687325516Percentage of physical writes compared to write requests (calculated value)
Key read ratio %3.17 %3.1674267100977Key cache miss calculated as rate of physical reads compared to read requests (calculated value)
Threads cache hitrate %99.99 %99.994810710502Thread cache hit rate (calculated value)