Letakkan berkas disini

SQL upload ( 0 ) x-

Server: 127.0.0.1:3309
Page-related settingsKlik pada bar untuk menggulir ke atas halaman
Tekan Ctrl+Enter untuk menjalankan kueriPress 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 Count: Time taken:
Bookmark
Segarkan
Tambah
Tidak ada bookmark
Tambah bookmark
Opsi
Kembalikan nilai bawaan





Tampilkan Buka Kueri ulang Ubah Jelaskan Profil Bookmarks Kueri gagal Basis data: Waktu eksekusi kueri:
Filters
VariabelNilaiDeskripsi
Aborted clientsDokumentasi1 Jumlah koneksi yang digugurkan karena klien terputus tanpa menutup koneksi dengan baik.
Aborted connectsDokumentasi16 Jumlah upaya koneksi ke server MySQL yang gagal.
Access denied errorsDokumentasi0
Acl column grantsDokumentasi0
Acl database grantsDokumentasi3
Acl function grantsDokumentasi0
Acl procedure grantsDokumentasi0
Acl proxy usersDokumentasi1
Acl role grantsDokumentasi0
Acl rolesDokumentasi0
Acl table grantsDokumentasi0
Acl usersDokumentasi6
Aria pagecache blocks not flushedDokumentasi0
Aria pagecache blocks unusedDokumentasi16 k
Aria pagecache blocks usedDokumentasi200
Aria pagecache read requestsDokumentasi35.9 M
Aria pagecache readsDokumentasi2.4 M
Aria pagecache write requestsDokumentasi4.9 M
Aria pagecache writesDokumentasi0
Aria transaction log syncsDokumentasi0
Binlog commitsDokumentasi0
Binlog group commitsDokumentasi0
Binlog group commit trigger countDokumentasi0
Binlog group commit trigger lock waitDokumentasi0
Binlog group commit trigger timeoutDokumentasi0
Binlog snapshot fileDokumentasi
Binlog snapshot positionDokumentasi0
Binlog bytes writtenDokumentasi0
Binlog cache disk useDokumentasi0Jumlah transaksi yang menggunakan singgahan log biner temporer, namun melebihi nilai binlog_cache_size dan menggunakan berkas temporer untuk menyimpan perintah dari transaksi.
Binlog cache useDokumentasi0Jumlah transaksi yang menggunakan singgahan log biner temporer.
Binlog stmt cache disk useDokumentasi0
Binlog stmt cache useDokumentasi0
Busy timeDokumentasi0
Bytes receivedDokumentasi12.6 G
Bytes sentDokumentasi36.3 G
Com admin commandsDokumentasi0
Com alter dbDokumentasi0
Com alter db upgradeDokumentasi0
Com alter eventDokumentasi0
Com alter functionDokumentasi0
Com alter procedureDokumentasi0
Com alter serverDokumentasi0
Com alter tableDokumentasi0
Com alter tablespaceDokumentasi0
Com analyzeDokumentasi0
Com assign to keycacheDokumentasi0
Com beginDokumentasi0
Com binlogDokumentasi0
Com call procedureDokumentasi1.2 k
Com change dbDokumentasi1.6 M
Com change masterDokumentasi0
Com checkDokumentasi0
Com checksumDokumentasi0
Com commitDokumentasi0
Com compound sqlDokumentasi0
Com create dbDokumentasi0
Com create eventDokumentasi0
Com create functionDokumentasi0
Com create indexDokumentasi0
Com create procedureDokumentasi0
Com create roleDokumentasi0
Com create serverDokumentasi0
Com create tableDokumentasi0
Com create temporary tableDokumentasi117
Com create triggerDokumentasi0
Com create udfDokumentasi0
Com create userDokumentasi0
Com create viewDokumentasi0
Com deleteDokumentasi2.6 M
Com delete multiDokumentasi0
Com doDokumentasi0
Com drop dbDokumentasi0
Com drop eventDokumentasi0
Com drop functionDokumentasi0
Com drop indexDokumentasi0
Com drop procedureDokumentasi0
Com drop roleDokumentasi0
Com drop serverDokumentasi0
Com drop tableDokumentasi117
Com drop temporary tableDokumentasi0
Com drop triggerDokumentasi0
Com drop userDokumentasi0
Com drop viewDokumentasi0
Com empty queryDokumentasi0
Com flushDokumentasi330.5 k
Com get diagnosticsDokumentasi0
Com grantDokumentasi0
Com grant roleDokumentasi0
Com ha closeDokumentasi0
Com ha openDokumentasi0
Com ha readDokumentasi0
Com helpDokumentasi0
Com insertDokumentasi1.3 M
Com insert selectDokumentasi117
Com install pluginDokumentasi0
Com killDokumentasi0
Com loadDokumentasi0
Com lock tablesDokumentasi0
Com optimizeDokumentasi0
Com preload keysDokumentasi0
Com purgeDokumentasi0
Com purge before dateDokumentasi0
Com release savepointDokumentasi0
Com rename tableDokumentasi0
Com rename userDokumentasi0
Com repairDokumentasi0
Com replaceDokumentasi63 k
Com replace selectDokumentasi0
Com resetDokumentasi0
Com resignalDokumentasi0
Com revokeDokumentasi0
Com revoke allDokumentasi0
Com revoke roleDokumentasi0
Com rollbackDokumentasi0
Com rollback to savepointDokumentasi0
Com savepointDokumentasi0
Com selectDokumentasi32 M
Com set optionDokumentasi663.7 k
Com show authorsDokumentasi0
Com show binlog eventsDokumentasi0
Com show binlogsDokumentasi50.1 k
Com show charsetsDokumentasi0
Com show collationsDokumentasi0
Com show contributorsDokumentasi0
Com show create dbDokumentasi0
Com show create eventDokumentasi0
Com show create funcDokumentasi12 k
Com show create procDokumentasi38.7 k
Com show create tableDokumentasi1.1 M
Com show create triggerDokumentasi0
Com show databasesDokumentasi0
Com show engine logsDokumentasi0
Com show engine mutexDokumentasi0
Com show engine statusDokumentasi0
Com show errorsDokumentasi0
Com show eventsDokumentasi0
Com show explainDokumentasi0
Com show fieldsDokumentasi2.3 M
Com show function statusDokumentasi0
Com show genericDokumentasi0
Com show grantsDokumentasi102.4 k
Com show keysDokumentasi2.7 M
Com show master statusDokumentasi150.1 k
Com show open tablesDokumentasi0
Com show pluginsDokumentasi14.3 k
Com show privilegesDokumentasi0
Com show procedure statusDokumentasi0
Com show processlistDokumentasi182
Com show profileDokumentasi0
Com show profilesDokumentasi0
Com show relaylog eventsDokumentasi0
Com show slave hostsDokumentasi0
Com show slave statusDokumentasi151.1 k
Com show statusDokumentasi1.2 k
Com show storage enginesDokumentasi10.7 k
Com show table statusDokumentasi1 k
Com show tablesDokumentasi527.1 k
Com show triggersDokumentasi0
Com show variablesDokumentasi109.1 k
Com show warningsDokumentasi0
Com shutdownDokumentasi0
Com signalDokumentasi0
Com start all slavesDokumentasi0
Com start slaveDokumentasi0
Com stmt closeDokumentasi873
Com stmt executeDokumentasi907
Com stmt fetchDokumentasi0
Com stmt prepareDokumentasi908
Com stmt reprepareDokumentasi0
Com stmt resetDokumentasi0
Com stmt send long dataDokumentasi0
Com stop all slavesDokumentasi0
Com stop slaveDokumentasi0
Com truncateDokumentasi0
Com uninstall pluginDokumentasi0
Com unlock tablesDokumentasi0
Com updateDokumentasi1.3 M
Com update multiDokumentasi0
Com xa commitDokumentasi0
Com xa endDokumentasi0
Com xa prepareDokumentasi0
Com xa recoverDokumentasi0
Com xa rollbackDokumentasi0
Com xa startDokumentasi0
CompressionDokumentasiOFF
Connection errors acceptDokumentasi0
Connection errors internalDokumentasi0
Connection errors max connectionsDokumentasi0
Connection errors peer addressDokumentasi0
Connection errors selectDokumentasi0
Connection errors tcpwrapDokumentasi0
ConnectionsDokumentasi663.9 kJumlah upaya koneksi ke server MySQL (baik berhasil maupun tidak).
Cpu timeDokumentasi0
Created tmp disk tablesDokumentasi2.7 MJumlah 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 filesDokumentasi13 Jumlah berkas temporer yang telah dibuat mysqld.
Created tmp tablesDokumentasi18.1 MJumlah tabel temporer dalam-memori yang dibuat otomatis oleh server sewaktu mengeksekusi perintah.
Delayed errorsDokumentasi0Jumlah baris yang ditulis oleh INSERT DELAYED yang menyebabkan beberapa galat (kemungkinan karena kunci duplikat).
Delayed insert threadsDokumentasi0Jumlah thread handler INSERT DELAYED yang dipakai. Setiap tabel berbeda yang menggunakan INSERT DELAYED mendapat satu thread sendiri.
Delayed writesDokumentasi0Jumlah baris INSERT DELAYED yang ditulis.
Delete scanDokumentasi1
Empty queriesDokumentasi19.3 M
Executed eventsDokumentasi0
Executed triggersDokumentasi0
Feature delay key writeDokumentasi0
Feature dynamic columnsDokumentasi0
Feature fulltextDokumentasi0
Feature gisDokumentasi0
Feature localeDokumentasi0
Feature subqueryDokumentasi749.6 k
Feature timezoneDokumentasi0
Feature triggerDokumentasi4.5 k
Feature xmlDokumentasi0
Flush commandsDokumentasi1 Jumlah perintah FLUSH yang dieksekusi.
Handler commitDokumentasi23 MJumlah perintah COMMIT internal.
Handler deleteDokumentasi1.3 MBerapa kali suatu baris dihapus dari suatu tabel.
Handler discoverDokumentasi52 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 lockDokumentasi0
Handler icp attemptsDokumentasi10.8 k
Handler icp matchDokumentasi8.3 k
Handler mrr initDokumentasi0
Handler mrr key refillsDokumentasi0
Handler mrr rowid refillsDokumentasi0
Handler prepareDokumentasi0
Handler read firstDokumentasi2.8 MBerapa 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 keyDokumentasi27.3 MJumlah permintaan membaca suatu baris berdasarkan suatu kunci. Nilai yang tinggi merupakan indikasi bagus bahwa kueri dan tabel Anda diindeks dengan baik.
Handler read lastDokumentasi18
Handler read nextDokumentasi3.3 GJumlah 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 prevDokumentasi0Jumlah permintaan membaca baris sebelumnya dalam urutan kunci. Metode baca ini terutama digunakan untuk mengoptimalkan ORDER BY … DESC.
Handler read retryDokumentasi0
Handler read rndDokumentasi16.7 MJumlah 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.5 M
Handler read rnd nextDokumentasi265 MJumlah 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 rollbackDokumentasi34 Jumlah perintah ROLLBACK internal.
Handler savepointDokumentasi0
Handler savepoint rollbackDokumentasi0
Handler tmp updateDokumentasi2.4 M
Handler tmp writeDokumentasi259.8 M
Handler updateDokumentasi63.7 kJumlah permintaan untuk memperbarui baris dalam tabel.
Handler writeDokumentasi1.4 MJumlah permintaan untuk menambah baris dalam tabel.
Innodb available undo logsDokumentasi128
Innodb background log syncDokumentasi910 k
Innodb buffer pool bytes dataDokumentasi116.6 M
Innodb buffer pool bytes dirtyDokumentasi671.7 k
Innodb buffer pool dump statusDokumentasiDumping buffer pool(s) not yet started
Innodb buffer pool load statusDokumentasiLoading buffer pool(s) not yet started
Innodb buffer pool pages dataDokumentasi7.1 kJumlah halaman yang mengandung data (kotor atau bersih).
Innodb buffer pool pages dirtyDokumentasi41 Jumlah halaman kotor saat ini.
Innodb buffer pool pages flushedDokumentasi254.2 kThe number of buffer pool pages that have been requested to be flushed.
Innodb buffer pool pages freeDokumentasi1 kJumlah halaman bebas.
Innodb buffer pool pages lru flushedDokumentasi0
Innodb buffer pool pages made not youngDokumentasi441.4 k
Innodb buffer pool pages made youngDokumentasi2.8 k
Innodb buffer pool pages miscDokumentasi53 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 oldDokumentasi2.6 k
Innodb buffer pool pages totalDokumentasi8.2 kTotal size of buffer pool, in pages.
Innodb buffer pool read aheadDokumentasi6.5 k
Innodb buffer pool read ahead evictedDokumentasi0
Innodb buffer pool read ahead rndDokumentasi0The 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 requestsDokumentasi505.6 MThe number of logical read requests InnoDB has done.
Innodb buffer pool readsDokumentasi3.7 kThe number of logical reads that InnoDB could not satisfy from buffer pool and had to do a single-page read.
Innodb buffer pool wait freeDokumentasi0Normally, 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 requestsDokumentasi610.8 kThe number writes done to the InnoDB buffer pool.
Innodb checkpoint ageDokumentasi17.8 k
Innodb checkpoint max ageDokumentasi53.6 M
Innodb data fsyncsDokumentasi229.8 kThe number of fsync() operations so far.
Innodb data pending fsyncsDokumentasi0Jumlah operasi fsync() tunda saat ini.
Innodb data pending readsDokumentasi0Jumlah baca tunda saat ini.
Innodb data pending writesDokumentasi0Jumlah tulis tunda saat ini.
Innodb data readDokumentasi170.3 MJumlah data yang dibaca sampai saat ini, dalam bita.
Innodb data readsDokumentasi10.9 kJumlah total baca data.
Innodb data writesDokumentasi424.2 kJumlah total tulis data.
Innodb data writtenDokumentasi4.2 GThe amount of data written so far, in bytes.
Innodb dblwr pages writtenDokumentasi254.2 kThe number of pages that have been written for doublewrite operations.
Innodb dblwr writesDokumentasi40.3 kThe number of doublewrite operations that have been performed.
Innodb deadlocksDokumentasi0
Innodb have atomic builtinsDokumentasiON
Innodb history list lengthDokumentasi20
Innodb ibuf discarded delete marksDokumentasi0
Innodb ibuf discarded deletesDokumentasi0
Innodb ibuf discarded insertsDokumentasi0
Innodb ibuf free listDokumentasi65
Innodb ibuf merged delete marksDokumentasi0
Innodb ibuf merged deletesDokumentasi0
Innodb ibuf merged insertsDokumentasi97
Innodb ibuf mergesDokumentasi96
Innodb ibuf segment sizeDokumentasi67
Innodb ibuf sizeDokumentasi1
Innodb log waitsDokumentasi0The 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 requestsDokumentasi212.6 kThe number of log write requests.
Innodb log writesDokumentasi97.8 kThe number of physical writes to the log file.
Innodb lsn currentDokumentasi47.4 G
Innodb lsn flushedDokumentasi47.4 G
Innodb lsn last checkpointDokumentasi47.4 G
Innodb master thread active loopsDokumentasi38.4 k
Innodb master thread idle loopsDokumentasi871.6 k
Innodb max trx idDokumentasi148.9 M
Innodb mem adaptive hashDokumentasi3.1 M
Innodb mem dictionaryDokumentasi3.2 M
Innodb mem totalDokumentasi137.6 M
Innodb mutex os waitsDokumentasi26.5 k
Innodb mutex spin roundsDokumentasi2 M
Innodb mutex spin waitsDokumentasi400.4 k
Innodb oldest view low limit trx idDokumentasi0
Innodb os log fsyncsDokumentasi128.2 kThe number of fsync() writes done to the log file.
Innodb os log pending fsyncsDokumentasi0The number of pending log file fsyncs.
Innodb os log pending writesDokumentasi0Pending log file writes.
Innodb os log writtenDokumentasi130.7 MThe number of bytes written to the log file.
Innodb page sizeDokumentasi16.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 createdDokumentasi595 The number of pages created.
Innodb pages readDokumentasi10.3 kJumlah halaman yang dibaca.
Innodb pages0 readDokumentasi513
Innodb pages writtenDokumentasi254.2 kJumlah halaman yang ditulis.
Innodb purge trx idDokumentasi148.9 M
Innodb purge undo noDokumentasi0
Innodb read views memoryDokumentasi1.1 M
Innodb row lock current waitsDokumentasi0The number of row locks currently being waited for.
Innodb row lock timeDokumentasi140 The total time spent in acquiring row locks, in milliseconds.
Innodb row lock time avgDokumentasi17 The average time to acquire a row lock, in milliseconds.
Innodb row lock time maxDokumentasi140 The maximum time to acquire a row lock, in milliseconds.
Innodb row lock waitsDokumentasi8 The number of times a row lock had to be waited for.
Innodb rows deletedDokumentasi642 Jumlah baris yang dihapus dari tabel InnoDB.
Innodb rows insertedDokumentasi1.5 kJumlah baris yang ditambahkan pada tabel InnoDB.
Innodb rows readDokumentasi3.3 GJumlah baris yang dibaca dari tabel InnoDB.
Innodb rows updatedDokumentasi63.7 kJumlah baris yang diperbarui pada tabel InnoDB.
Innodb system rows deletedDokumentasi0
Innodb system rows insertedDokumentasi0
Innodb system rows readDokumentasi703 k
Innodb system rows updatedDokumentasi0
Innodb s lock os waitsDokumentasi23.9 k
Innodb s lock spin roundsDokumentasi910.7 k
Innodb s lock spin waitsDokumentasi30.4 k
Innodb truncated status writesDokumentasi0
Innodb x lock os waitsDokumentasi965
Innodb x lock spin roundsDokumentasi29.2 k
Innodb x lock spin waitsDokumentasi72
Innodb page compression savedDokumentasi0
Innodb page compression trim sect512Dokumentasi0
Innodb page compression trim sect1024Dokumentasi0
Innodb page compression trim sect2048Dokumentasi0
Innodb page compression trim sect4096Dokumentasi0
Innodb page compression trim sect8192Dokumentasi0
Innodb page compression trim sect16384Dokumentasi0
Innodb page compression trim sect32768Dokumentasi0
Innodb num index pages writtenDokumentasi25.2 k
Innodb num non index pages writtenDokumentasi398.8 k
Innodb num pages page compressedDokumentasi0
Innodb num page compressed trim opDokumentasi0
Innodb num page compressed trim op savedDokumentasi0
Innodb num pages page decompressedDokumentasi0
Innodb num pages page compression errorDokumentasi0
Innodb num pages encryptedDokumentasi0
Innodb num pages decryptedDokumentasi0
Innodb have lz4DokumentasiOFF
Innodb have lzoDokumentasiOFF
Innodb have lzmaDokumentasiOFF
Innodb have bzip2DokumentasiOFF
Innodb have snappyDokumentasiOFF
Innodb defragment compression failuresDokumentasi0
Innodb defragment failuresDokumentasi0
Innodb defragment countDokumentasi0
Innodb onlineddl rowlog rowsDokumentasi0
Innodb onlineddl rowlog pct usedDokumentasi0
Innodb onlineddl pct progressDokumentasi0
Innodb secondary index triggered cluster readsDokumentasi1.5 M
Innodb secondary index triggered cluster reads avoidedDokumentasi0
Innodb encryption rotation pages read from cacheDokumentasi0
Innodb encryption rotation pages read from diskDokumentasi0
Innodb encryption rotation pages modifiedDokumentasi0
Innodb encryption rotation pages flushedDokumentasi0
Innodb encryption rotation estimated iopsDokumentasi0
Innodb encryption key rotation list lengthDokumentasi0
Innodb encryption n merge blocks encryptedDokumentasi0
Innodb encryption n merge blocks decryptedDokumentasi0
Innodb encryption n rowlog blocks encryptedDokumentasi0
Innodb encryption n rowlog blocks decryptedDokumentasi0
Innodb scrub background page reorganizationsDokumentasi0
Innodb scrub background page splitsDokumentasi0
Innodb scrub background page split failures underflowDokumentasi0
Innodb scrub background page split failures out of filespaceDokumentasi0
Innodb scrub background page split failures missing indexDokumentasi0
Innodb scrub background page split failures unknownDokumentasi0
Innodb encryption num key requestsDokumentasi0
Key blocks not flushedDokumentasi0The 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 unusedDokumentasi14.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 usedDokumentasi29 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 warmDokumentasi4
Key read requestsDokumentasi30 MThe number of requests to read a key block from the cache.
Key readsDokumentasi38 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 requestsDokumentasi18.2 MThe number of requests to write a key block to the cache.
Key writesDokumentasi13.9 MThe number of physical writes of a key block to disk.
Last query costDokumentasi0The 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 countDokumentasi0
Master gtid wait timeDokumentasi0
Master gtid wait timeoutsDokumentasi0
Max statement time exceededDokumentasi0
Max used connectionsDokumentasi42 The maximum number of connections that have been in use simultaneously since the server started.
Memory usedDokumentasi167.3 M
Not flushed delayed rowsDokumentasi0The number of rows waiting to be written in INSERT DELAYED queues.
Open filesDokumentasi137 Jumlah file yang terbuka.
Open streamsDokumentasi0The number of streams that are open (used mainly for logging).
Open table definitionsDokumentasi360
Open tablesDokumentasi756 Jumlah tabel yang terbuka.
Opened filesDokumentasi10.9 M
Opened plugin librariesDokumentasi0
Opened table definitionsDokumentasi587
Opened tablesDokumentasi884 The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
Opened viewsDokumentasi794.2 k
Performance schema accounts lostDokumentasi0
Performance schema cond classes lostDokumentasi0
Performance schema cond instances lostDokumentasi0
Performance schema digest lostDokumentasi0
Performance schema file classes lostDokumentasi0
Performance schema file handles lostDokumentasi0
Performance schema file instances lostDokumentasi0
Performance schema hosts lostDokumentasi0
Performance schema locker lostDokumentasi0
Performance schema mutex classes lostDokumentasi0
Performance schema mutex instances lostDokumentasi0
Performance schema rwlock classes lostDokumentasi0
Performance schema rwlock instances lostDokumentasi0
Performance schema session connect attrs lostDokumentasi0
Performance schema socket classes lostDokumentasi0
Performance schema socket instances lostDokumentasi0
Performance schema stage classes lostDokumentasi0
Performance schema statement classes lostDokumentasi0
Performance schema table handles lostDokumentasi0
Performance schema table instances lostDokumentasi0
Performance schema thread classes lostDokumentasi0
Performance schema thread instances lostDokumentasi0
Performance schema users lostDokumentasi0
Prepared stmt countDokumentasi0
Qcache free blocksDokumentasi1 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 memoryDokumentasi1 MJumlah memori kosong untuk cache query.
Qcache hitsDokumentasi0The number of cache hits.
Qcache insertsDokumentasi0The number of queries added to the cache.
Qcache lowmem prunesDokumentasi0The 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 cachedDokumentasi0The number of non-cached queries (not cachable, or not cached due to the query_cache_type setting).
Qcache queries in cacheDokumentasi0The number of queries registered in the cache.
Qcache total blocksDokumentasi1 The total number of blocks in the query cache.
QueriesDokumentasi47.9 M
QuestionsDokumentasi47.9 M
Rows readDokumentasi3.3 G
Rows sentDokumentasi140 M
Rows tmp readDokumentasi258.3 M
Rpl statusDokumentasiAUTH_MASTERThe status of failsafe replication (not yet implemented).
Select full joinDokumentasi323.4 kThe 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 joinDokumentasi0The number of joins that used a range search on a reference table.
Select rangeDokumentasi103 The number of joins that used ranges on the first table. (It's normally not critical even if this is big.)
Select range checkDokumentasi0The 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 scanDokumentasi17 MThe number of joins that did a full scan of the first table.
Slave connectionsDokumentasi0
Slave heartbeat periodDokumentasi0
Slave open temp tablesDokumentasi0The number of temporary tables currently open by the slave SQL thread.
Slave received heartbeatsDokumentasi0
Slave retried transactionsDokumentasi0Total (since startup) number of times the replication slave SQL thread has retried transactions.
Slave runningDokumentasiOFFThis is ON if this server is a slave that is connected to a master.
Slave skipped errorsDokumentasi0
Slaves connectedDokumentasi0
Slaves runningDokumentasi0
Slow launch threadsDokumentasi0The number of threads that have taken more than slow_launch_time seconds to create.
Slow queriesDokumentasi0The number of queries that have taken more than long_query_time seconds.Dokumentasi
Sort merge passesDokumentasi4 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 sortsDokumentasi1 k
Sort rangeDokumentasi991 The number of sorts that were done with ranges.
Sort rowsDokumentasi16.7 MJumlah baris diurutkan.
Sort scanDokumentasi1.3 MThe number of sorts that were done by scanning the table.
Ssl accept renegotiatesDokumentasi0
Ssl acceptsDokumentasi0
Ssl callback cache hitsDokumentasi0
Ssl cipherDokumentasi
Ssl cipher listDokumentasi
Ssl client connectsDokumentasi0
Ssl connect renegotiatesDokumentasi0
Ssl ctx verify depthDokumentasi0
Ssl ctx verify modeDokumentasi0
Ssl default timeoutDokumentasi0
Ssl finished acceptsDokumentasi0
Ssl finished connectsDokumentasi0
Ssl server not afterDokumentasi
Ssl server not beforeDokumentasi
Ssl session cache hitsDokumentasi0
Ssl session cache missesDokumentasi0
Ssl session cache modeDokumentasiNONE
Ssl session cache overflowsDokumentasi0
Ssl session cache sizeDokumentasi0
Ssl session cache timeoutsDokumentasi0
Ssl sessions reusedDokumentasi0
Ssl used session cache entriesDokumentasi0
Ssl verify depthDokumentasi0
Ssl verify modeDokumentasi0
Ssl versionDokumentasi
Subquery cache hitDokumentasi0
Subquery cache missDokumentasi10.4 k
SyncsDokumentasi3
Table locks immediateDokumentasi33.5 MThe number of times that a table lock was acquired immediately.
Table locks waitedDokumentasi2.6 kThe 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.
Tc log max pages usedDokumentasi0
Tc log page sizeDokumentasi0
Tc log page waitsDokumentasi0
Threadpool idle threadsDokumentasi0
Threadpool threadsDokumentasi6
Threads cachedDokumentasi0The 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 connectedDokumentasi4 Jumlah koneksi yang sedang terbuka.
Threads createdDokumentasi1.6 kThe 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 runningDokumentasi1 The number of threads that are not sleeping.
Update scanDokumentasi0
UptimeDokumentasi10 hari, 14 jam, 54 menit dan 20 detik
Uptime since flush statusDokumentasi10 hari, 14 jam, 54 menit dan 20 detik
Key buffer fraction %12.63 %Percentage of used key cache (calculated value)
Key write ratio %76.36 %Percentage of physical writes compared to write requests (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.76 %Thread cache hit rate (calculated value)