{"parse":{"errors":[]},"run":{"fired":[{"name":"Waktu kueri panjang","precondition":"!PMA_DRIZZLE","formula":"long_query_time","test":"value >= 10","issue":"{long_query_time} is set to 10 seconds or more, thus only slow queries that take above 10 seconds are logged.","recommendation":"It is suggested to set <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=long_query_time\">long_query_time<\/a> to a lower value, depending on your environment. Usually a value of 1-5 seconds is suggested.","justification":"long_query_time is currently set to 10s.","id":"Long query time"},{"name":"Log kueri lambat","precondition":"!PMA_DRIZZLE && PMA_MYSQL_INT_VERSION >= 50600","formula":"slow_query_log","test":"value == 'OFF'","issue":"The slow query log is disabled.","recommendation":"Enable slow query logging by setting <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=slow_query_log\">slow_query_log<\/a> to 'ON'. This will help troubleshooting badly performing queries.","justification":"slow_query_log is set to 'OFF'","id":"Slow query logging"},{"name":"Singgahan kueri dinonaktifkan","precondition":"!PMA_DRIZZLE","formula":"query_cache_size","test":"value == 0 || query_cache_type == 'OFF' || query_cache_type == '0'","issue":"Singgahan kueri tidak diaktifkan.","recommendation":"The query cache is known to greatly improve performance if configured correctly. Enable it by setting <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=query_cache_size\">query_cache_size<\/a> to a 2 digit MiB value and setting <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=query_cache_type\">query_cache_type<\/a> to 'ON'. <b>Note:<\/b> If you are using memcached, ignore this recommendation.","justification":"query_cache_size is set to 0 or query_cache_type is set to 'OFF'","id":"Query cache disabled"},{"name":"Urutkan baris","formula":"Sort_rows \/ Uptime","test":"value * 60 >= 1","issue":"There are lots of rows being sorted.","recommendation":"While there is nothing wrong with a high amount of row sorting, you might want to make sure that the queries which require a lot of sorting use indexed columns in the ORDER BY clause, as this will result in much faster sorting","justification":"Sorted rows average: 3.32 per detik","id":"Sort rows"},{"name":"Laju join tanpa indeks","formula":"(Select_range_check + Select_scan + Select_full_join) \/ Uptime","test":"value * 60 * 60 > 1","issue":"Terlalu banyak join tanpa indeks.","recommendation":"This means that joins are doing full table scans. Adding indexes for the columns being used in the join conditions will greatly speed up table joins","justification":"Table joins average: 3.19 per detik, this value should be less than 1 per hour","id":"Rate of joins without indexes"},{"name":"Rate of reading first index entry","formula":"Handler_read_first \/ Uptime","test":"value * 60 * 60 > 1","issue":"The rate of reading the first index entry is high.","recommendation":"This usually indicates frequent full index scans. Full index scans are faster than table scans but require lots of CPU cycles in big tables, if those tables that have or had high volumes of UPDATEs and DELETEs, running 'OPTIMIZE TABLE' might reduce the amount of and\/or speed up full index scans. Other than that full index scans can only be reduced by rewriting queries.","justification":"Index scans average: 38.04 per menit, this value should be less than 1 per hour","id":"Rate of reading first index entry"},{"name":"Rate of reading fixed position","formula":"Handler_read_rnd \/ Uptime","test":"value * 60 * 60 > 1","issue":"The rate of reading data from a fixed position is high.","recommendation":"This indicates that many queries need to sort results and\/or do a full table scan, including join queries that do not use indexes. Add indexes where applicable.","justification":"Rate of reading fixed position average: 3.32 per detik, this value should be less than 1 per hour","id":"Rate of reading fixed position"},{"name":"Rate of reading next table row","formula":"Handler_read_rnd_next \/ Uptime","test":"value * 60 * 60 > 1","issue":"The rate of reading the next table row is high.","recommendation":"This indicates that many queries are doing full table scans. Add indexes where applicable.","justification":"Rate of reading next table row: 58.99 per detik, this value should be less than 1 per hour","id":"Rate of reading next table row"},{"name":"Tingkat diska temporer","precondition":"!fired('Percentage of temp tables on disk')","formula":"Created_tmp_disk_tables \/ Uptime","test":"value * 60 * 60 > 1","issue":"Many temporary tables are being written to disk instead of being kept in memory.","recommendation":"Increasing <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=max_heap_table_size\">max_heap_table_size<\/a> and <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=tmp_table_size\">tmp_table_size<\/a> might help. However some temporary tables are always being written to disk, independent of the value of these variables. To eliminate these you will have to rewrite your queries to avoid those conditions (Within a temporary table: Presence of a BLOB or TEXT column or presence of a column bigger than 512 bytes) as mentioned in the <a href=\".\/url.php?url=http%3A%2F%2Fdev.mysql.com%2Fdoc%2Frefman%2F5.5%2Fen%2Finternal-temporary-tables.html\" target=\"_blank\">MySQL Documentation<\/a>","justification":"Tingkat pembuatan tabel temporer ke diska: 23.4 per menit, nilai ini hasul kurang dari 1 per jam","id":"Temp disk rate"},{"name":"Jumlah % maksimum penyangga kunci MyISAM yang pernah dipakai","precondition":"!PMA_DRIZZLE && key_buffer_size > 0","formula":"Key_blocks_used * key_cache_block_size \/ key_buffer_size * 100","test":"value < 95","issue":"Penyangga kunci MyISAM (singgahan indeks) % yang dipakai rendah.","recommendation":"You may need to decrease the size of <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=key_buffer_size\">key_buffer_size<\/a>, re-examine your tables to see if indexes have been removed, or examine queries and expectations about what indexes are being used.","justification":"max % MyISAM key buffer ever used: 0.2%, this value should be above 95%","id":"Max % MyISAM key buffer ever used"},{"name":"Tingkat tunggu kunci tabel","formula":"Table_locks_waited \/ Uptime","test":"value * 60 * 60 > 1","issue":"Too many table locks were not granted immediately.","recommendation":"Optimize queries and\/or use InnoDB to reduce lock wait.","justification":"Tingkat tunggu kunci tabel: 1.89 dalam sejam, hasil ini seharusnya kurang dari 1 per jam","id":"Table lock wait rate"},{"name":"Singgahan thread","precondition":"!PMA_DRIZZLE","formula":"thread_cache_size","test":"value < 1","issue":"Cache Thread dinonaktifkan, akibat kelebihan beban dari koneksi baru ke MySQL.","recommendation":"Aktifkan cache thread dengan mengatur <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=thread_cache_size\">thread_cache_size<\/a> > 0.","justification":"Cache thread diatur ke 0","id":"Thread cache"}],"notfired":[{"name":"Uptime kurang dari satu hari","formula":"Uptime","test":"value < 86400","issue":"Uptime is less than 1 day, performance tuning may not be accurate.","recommendation":"To have more accurate averages it is recommended to let the server run for longer than a day before running this analyzer","justification":"Uptime hanya 10 hari, 2 jam, 50 menit dan 5 detik","id":"Uptime below one day"},{"name":"Perintah di bawah 1.000","formula":"Questions","test":"value < 1000","issue":"Kurang dari 1.000 perintah telah dijalankan oleh server ini. Rekomendasi mungkin tidak akurat.","recommendation":"Let the server run for a longer time until it has executed a greater amount of queries.","justification":"Jumlah Perintah saat ini: 6321234","id":"Questions below 1,000"},{"name":"Persentase kueri lambat","precondition":"Questions > 0 && !PMA_DRIZZLE","formula":"Slow_queries \/ Questions * 100","test":"value >= 5","issue":"There is a lot of slow queries compared to the overall amount of Queries.","recommendation":"You might want to increase <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=long_query_time\">long_query_time<\/a> or optimize the queries listed in the slow query log","justification":"Tingkat lambat permintaan harus di bawah 5%, nilai Anda adalah 0%.","id":"Percentage of slow queries"},{"name":"Laju kueri lambat","precondition":"Questions > 0","formula":"(Slow_queries \/ Questions * 100) \/ Uptime","test":"value * 60 * 60 > 1","issue":"There is a high percentage of slow queries compared to the server uptime.","recommendation":"You might want to increase <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=long_query_time\">long_query_time<\/a> or optimize the queries listed in the slow query log","justification":"You have a slow query rate of <0.01 per hari per hour, you should have less than 1% per hour.","id":"Slow query rate"},{"name":"Seri Rilis","precondition":"!PMA_DRIZZLE","formula":"version","test":"substr(value,0,2) <= '5.' && substr(value,2,1) < 1","issue":"Versi Server MySQL dibawah 5.1.","recommendation":"You should upgrade, as MySQL 5.1 has improved performance, and MySQL 5.5 even more so.","justification":"Versi saat ini: 10.1.30-MariaDB","id":"Release Series"},{"name":"Versi Minor","precondition":"! fired('Release Series')","formula":"version","test":"substr(value,0,2) <= '5.' && substr(value,2,1) <= 1 && substr(value,4,2) < 30","issue":"Version less than 5.1.30 (the first GA release of 5.1).","recommendation":"You should upgrade, as recent versions of MySQL 5.1 have improved performance and MySQL 5.5 even more so.","justification":"Versi saat ini: 10.1.30-MariaDB","id":"Minor Version"},{"name":"Versi Minor","precondition":"! fired('Release Series')","formula":"version","test":"substr(value,0,1) == 5 && substr(value,2,1) == 5 && substr(value,4,2) < 8","issue":"Version less than 5.5.8 (the first GA release of 5.5).","recommendation":"Anda harus memperbarui ke versi stabil MySQL 5.5","justification":"Versi saat ini: 10.1.30-MariaDB","id":"Minor Version"},{"name":"Distribusi","formula":"version_comment","test":"preg_match('\/source\/i',value)","issue":"Version is compiled from source, not a MySQL official binary.","recommendation":"If you did not compile from source, you may be using a package modified by a distribution. The MySQL manual only is accurate for official MySQL binaries, not any package distributions (such as RedHat, Debian\/Ubuntu etc).","justification":"'source' ditemukan pada version_comment","id":"Distribution"},{"name":"Distribusi","formula":"version_comment","test":"preg_match('\/percona\/i',value)","issue":"The MySQL manual only is accurate for official MySQL binaries.","recommendation":"Percona documentation is at <a href=\".\/url.php?url=http%3A%2F%2Fwww.percona.com%2Fsoftware%2Fdocumentation%2F\" target=\"_blank\">http:\/\/www.percona.com\/software\/documentation\/<\/a>","justification":"'percona' ditemukan pada version_comment","id":"Distribution"},{"name":"Distribusi","formula":"version","test":"PMA_DRIZZLE","issue":"The MySQL manual only is accurate for official MySQL binaries.","recommendation":"Drizzle documentation is at <a href=\".\/url.php?url=http%3A%2F%2Fwww.drizzle.org%2Fcontent%2Fdocumentation%2F\" target=\"_blank\">http:\/\/www.drizzle.org\/content\/documentation\/<\/a>","justification":"Version string (10.1.30-MariaDB) matches Drizzle versioning scheme","id":"Distribution"},{"name":"Arsitektur MySQL","formula":"system_memory","test":"value > 3072*1024 && !preg_match('\/64\/',version_compile_machine) && !preg_match('\/64\/',version_compile_os)","issue":"MySQL is not compiled as a 64-bit package.","recommendation":"Your memory capacity is above 3 GiB (assuming the Server is on localhost), so MySQL might not be able to access all of your memory. You might want to consider installing the 64-bit version of MySQL.","justification":"Available memory on this host: 0 B","id":"MySQL Architecture"},{"name":"Persentase pengurutan yang menyebabkan tabel temporer","precondition":"Sort_scan + Sort_range > 0","formula":"Sort_merge_passes \/ (Sort_scan + Sort_range) * 100","test":"value > 10","issue":"Terlalu banyak pengurutan yang menyebabkan tabel temporer.","recommendation":"Consider increasing <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=sort_buffer_size\">sort_buffer_size<\/a> and\/or <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=read_rnd_buffer_size\">read_rnd_buffer_size<\/a>, depending on your system memory limits","justification":"0% of all sorts cause temporary tables, this value should be lower than 10%.","id":"Percentage of sorts that cause temporary tables"},{"name":"Laju pengurutan yang menyebabkan tabel temporer","formula":"Sort_merge_passes \/ Uptime","test":"value * 60 * 60 > 1","issue":"Terlalu banyak pengurutan yang menyebabkan tabel temporer.","recommendation":"Consider increasing <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=sort_buffer_size\">sort_buffer_size<\/a> and\/or <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=read_rnd_buffer_size\">read_rnd_buffer_size<\/a>, depending on your system memory limits","justification":"Temporary tables average: 0.3 per hari, this value should be less than 1 per hour.","id":"Rate of sorts that cause temporary tables"},{"name":"Different tmp_table_size and max_heap_table_size","formula":"tmp_table_size - max_heap_table_size","test":"value !=0","issue":"{tmp_table_size} dan {max_heap_table_size} tidak sama.","recommendation":"If you have deliberately changed one of either: The server uses the lower value of either to determine the maximum size of in-memory tables. So if you wish to increase the in-memory table limit you will have to increase the other value as well.","justification":"Current values are tmp_table_size: 16 MB, max_heap_table_size: 16 MB","id":"Different tmp_table_size and max_heap_table_size"},{"name":"Percentage of temp tables on disk","precondition":"Created_tmp_tables + Created_tmp_disk_tables > 0","formula":"Created_tmp_disk_tables \/ (Created_tmp_tables + Created_tmp_disk_tables) * 100","test":"value > 25","issue":"Many temporary tables are being written to disk instead of being kept in memory.","recommendation":"Increasing <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=max_heap_table_size\">max_heap_table_size<\/a> and <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=tmp_table_size\">tmp_table_size<\/a> might help. However some temporary tables are always being written to disk, independent of the value of these variables. To eliminate these you will have to rewrite your queries to avoid those conditions (Within a temporary table: Presence of a BLOB or TEXT column or presence of a column bigger than 512 bytes) as mentioned in the beginning of an <a href=\".\/url.php?url=http%3A%2F%2Fwww.facebook.com%2Fnote.php%3Fnote_id%3D10150111255065841%26comments\" target=\"_blank\">Article by the Pythian Group<\/a>","justification":"10.3% of all temporary tables are being written to disk, this value should be below 25%","id":"Percentage of temp tables on disk"},{"name":"Ukuran penyangga kunci MyISAM","precondition":"!PMA_DRIZZLE","formula":"key_buffer_size","test":"value == 0","issue":"Key buffer is not initialized. No MyISAM indexes will be cached.","recommendation":"Set <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=key_buffer_size\">key_buffer_size<\/a> tergantung pada ukuran indeks MyISAM Anda. 64M adalah awal yang baik.","justification":"key_buffer_size is 0","id":"MyISAM key buffer size"},{"name":"Percentage of index reads from memory","precondition":"!PMA_DRIZZLE && Key_read_requests > 0","formula":"100 - (Key_reads \/ Key_read_requests * 100)","test":"value < 95","issue":"The % of indexes that use the MyISAM key buffer is low.","recommendation":"You may need to increase <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=key_buffer_size\">key_buffer_size<\/a>.","justification":"Index reads from memory: 100%, this value should be above 95%","id":"Percentage of index reads from memory"},{"name":"Tingkat tabel yang terbuka","precondition":"!PMA_DRIZZLE","formula":"Opened_tables \/ Uptime","test":"value*60*60 > 10","issue":"The rate of opening tables is high.","recommendation":"Opening tables requires disk I\/O which is costly. Increasing <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=table_open_cache\">table_open_cache<\/a> might avoid this.","justification":"Opened table rate: 2.93 dalam sejam, this value should be less than 10 per hour","id":"Rate of table open"},{"name":"Persentase limit berkas terbuka yang dipakai","precondition":"!PMA_DRIZZLE","formula":"Open_files \/ open_files_limit * 100","test":"value > 85","issue":"Jumlah file yang terbuka mendekati jumlah maksimum file yang terbuka. Anda mungkin mendapatkan \"Terlalu banyak membuka file\" error.","recommendation":"Pertimbangkan untuk meningkatkan <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=open_files_limit\">open_files_limit<\/a>, dan periksa log kesalahan ketika restart setelah mengubah <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=open_files_limit\">open_files_limit<\/a>.","justification":"jumlah file yang dibuka adalah 2% dari batasan. seharusnya itu dibawah 85%","id":"Percentage of used open files limit"},{"name":"Tingkat berkas yang terbuka","precondition":"!PMA_DRIZZLE","formula":"Open_files \/ Uptime","test":"value * 60 * 60 > 5","issue":"The rate of opening files is high.","recommendation":"Pertimbangkan untuk meningkatkan <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=open_files_limit\">open_files_limit<\/a>, dan periksa log kesalahan ketika restart setelah mengubah <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=open_files_limit\">open_files_limit<\/a>.","justification":"Tingkat file yang dibuka: 12.26 per hari, seharusnya nilai ini kurang dari 5 per jam","id":"Rate of open files"},{"name":"Kunci tabel langsung %","precondition":"Table_locks_waited + Table_locks_immediate > 0","formula":"Table_locks_immediate \/ (Table_locks_waited + Table_locks_immediate) * 100","test":"value < 95","issue":"Too many table locks were not granted immediately.","recommendation":"Optimize queries and\/or use InnoDB to reduce lock wait.","justification":"Kunci tabel terpakai: 100%, seharusnya nilai ini diatas 95%","id":"Immediate table locks %"},{"name":"Threads that are slow to launch","precondition":"!PMA_DRIZZLE && slow_launch_time > 0","formula":"Slow_launch_threads","test":"value > 0","issue":"Terlalu banyak thread sehingga lambat untuk diluncurkan.","recommendation":"Hal ini biasanya terjadi dalam kasus overload sistem umum karena operasi cukup sederhana. Mungkin anda perlu memantau beban sistem anda dengan hati-hati.","justification":"thread 0 sepertinya dimulai lebih dari 2 detik, seharusnya ini dimulai dari 0","id":"Threads that are slow to launch"},{"name":"Waktu peluncuran lambat","precondition":"!PMA_DRIZZLE","formula":"slow_launch_time","test":"value > 2","issue":"Slow_launch_threads diatas 2 detik","recommendation":"Atur <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=slow_launch_time\">slow_launch_time<\/a> menjadi 1 atau 2 detik untuk memperbaiki perhitungan thread yang lambat diluncurkan","justification":"slow_launch_time disetel menjadi 2 detik","id":"Slow launch time"},{"name":"Persentase koneksi terpakai","precondition":"!PMA_DRIZZLE","formula":"Max_used_connections \/ max_connections * 100","test":"value > 80","issue":"Jumlah maksimum koneksi yang digunakan semakin mendekati nilai {max_connections}.","recommendation":"Menaikan<a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=max_connections\">max_connections<\/a>, atau mengurangi <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=wait_timeout\">wait_timeout<\/a> sehingga tidak menutupi penanganan basis data dengan baik, dapat mematikannya. Pastikan kode menutupi penanganan basis data dengan benar.","justification":"Max_used_connections saat ini mencapai 23.8% dari max_connections, itu seharusnya dibawah 80%","id":"Percentage of used connections"},{"name":"Persentasi koneksi yang digugurkan","formula":"Aborted_connects \/ Connections * 100","test":"value > 1","issue":"Terlalu banyak koneksi yang dibatalkan.","recommendation":"Connections are usually aborted when they cannot be authorized. <a href=\".\/url.php?url=http%3A%2F%2Fwww.percona.com%2Fblog%2F2008%2F08%2F23%2Fhow-to-track-down-the-source-of-aborted_connects%2F\" target=\"_blank\">This article<\/a> might help you track down the source.","justification":"0% dari semua koneksi dibatalkan. Nilai ini seharusnya dibawah 1%","id":"Percentage of aborted connections"},{"name":"Tingkat pengguguran koneksi","formula":"Aborted_connects \/ Uptime","test":"value * 60 * 60 > 1","issue":"Terlalu banyak koneksi yang dibatalkan.","recommendation":"Connections are usually aborted when they cannot be authorized. <a href=\".\/url.php?url=http%3A%2F%2Fwww.percona.com%2Fblog%2F2008%2F08%2F23%2Fhow-to-track-down-the-source-of-aborted_connects%2F\" target=\"_blank\">This article<\/a> might help you track down the source.","justification":"Tingkat koneksi yang digugurkan adalah pada 0.3 per hari, hasil ini seharusnya kurang dari 1 per jam","id":"Rate of aborted connections"},{"name":"Persentase klien yang digugurkan","formula":"Aborted_clients \/ Connections * 100","test":"value > 2","issue":"Terlalu banyak klien yang dibatalkan.","recommendation":"Klien biasanya digugurkan apabila mereka tidak menutup koneksi ke MySQL secara benar. Hal ini bisa disebabkan oleh adanya masalah pada jaringan atau kode tidak menutup handler basis data dengan benar. Periksa jaringan dan kode Anda.","justification":"0% dari semua klien dibatalkan. Nilai ini seharusnya dibawah 2%","id":"Percentage of aborted clients"},{"name":"Tingkat pengguguran klien","formula":"Aborted_clients \/ Uptime","test":"value * 60 * 60 > 1","issue":"Terlalu banyak klien yang dibatalkan.","recommendation":"Klien biasanya digugurkan apabila mereka tidak menutup koneksi ke MySQL secara benar. Hal ini bisa disebabkan oleh adanya masalah pada jaringan atau kode tidak menutup handler basis data dengan benar. Periksa jaringan dan kode Anda.","justification":"Tingkat koneksi yang digugurkan adalah pada <0.01 per hari, nilai ini seharusnya kurang dari 1 per jam","id":"Rate of aborted clients"},{"name":"Besar log InnoDB","precondition":"innodb_buffer_pool_size > 0","formula":"innodb_log_file_size \/ innodb_buffer_pool_size * 100","test":"value < 20 && innodb_log_file_size \/ (1024 * 1024) < 256","issue":"ukuran file log InnoDB tidak pada ukuran yang sesuai, dalam kaitannya dengan buffer pool InnoDB.","recommendation":"Terutama pada sistem yang banyak melakukan penulisan ke tabel InnoDB anda seharusnya menetapkan nilai <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=innodb_log_file_size\">innodb_log_file_size<\/a> ke 25% dari <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=innodb_buffer_pool_size\">innodb_buffer_pool_size<\/a>. Namun semakin besar nilai ini, semakin lama waktu pemulihan ketika terjadi kerusakan pada basis data, sehingga nilai ini tidak boleh diatur lebih dari 256 MiB. Perlu diingat bahwa anda tidak dapat dengan mudah mengganti nilai variabel ini. Anda perlu mematikan server, hapus file log InnoDB, menetapkan nilai baru di my.cnf, hidupkan server, kemudian cek log error untuk memastikan semuanya berjalan baik. Lihat juga <a href=\".\/url.php?url=http%3A%2F%2Fmysqldatabaseadministration.blogspot.com%2F2007%2F01%2Fincrease-innodblogfilesize-proper-way.html\" target=\"_blank\">entri blog ini<\/a>","justification":"Ukuran log InnoDB anda adalah 25% terkait dengan ukuran pool InnoDB, ini harus diatas 20%","id":"InnoDB log size"},{"name":"Ukuran maksimum log InnoDB","precondition":"innodb_buffer_pool_size > 0 && innodb_log_file_size \/ innodb_buffer_pool_size * 100 < 30","formula":"innodb_log_file_size \/ (1024 * 1024)","test":"value > 256","issue":"Ukuran file log InnoDB kurang besar.","recommendation":"It is usually sufficient to set <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=innodb_log_file_size\">innodb_log_file_size<\/a> to 25% of the size of <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=innodb_buffer_pool_size\">innodb_buffer_pool_size<\/a>. A very big <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=innodb_log_file_size\">innodb_log_file_size<\/a> slows down the recovery time after a database crash considerably. See also <a href=\".\/url.php?url=http%3A%2F%2Fwww.percona.com%2Fblog%2F2006%2F07%2F03%2Fchoosing-proper-innodb_log_file_size%2F%22%3Ethis+Article%3C%2Fa%3E.+You+need+to+shutdown+the+server%2C+remove+the+InnoDB+log+files%2C+set+the+new+value+in+my.cnf%2C+start+the+server%2C+then+check+the+error+logs+if+everything+went+fine.+See+also+%3Ca+href%3D%22http%3A%2F%2Fmysqldatabaseadministration.blogspot.com%2F2007%2F01%2Fincrease-innodblogfilesize-proper-way.html\" target=\"_blank\">this blog entry<\/a>","justification":"Ukuran absolut log InnoDB anda adalah 32 MiB","id":"Max InnoDB log size"},{"name":"Sisipan konkuren MyISAM","precondition":"!PMA_DRIZZLE","formula":"concurrent_insert","test":"value === 0 || value === 'NEVER'","issue":"Aktifkan {concurrent_insert} dengan menetapkan ke 1","recommendation":"Pengaturan <a href=\"server_variables.php?token=bbdfd96ea9fcd3e2d343bc36531cad33&filter=concurrent_insert\">concurrent_insert<\/a> ke 1 mengurangi pertentangan antara pembacaan dan penulisan pada tabel yang ditentukan. Lihat juga <a href=\".\/url.php?url=http%3A%2F%2Fdev.mysql.com%2Fdoc%2Frefman%2F5.5%2Fen%2Fconcurrent-inserts.html\" target=\"_blank\">Dokumentasi MySQL<\/a>","justification":"concurrent_insert diatur ke 0","id":"MyISAM concurrent inserts"}],"unchecked":[{"name":"Slow query logging","precondition":"!PMA_DRIZZLE && PMA_MYSQL_INT_VERSION < 50600","formula":"log_slow_queries","test":"value == 'OFF'","issue":"The slow query log is disabled.","recommendation":"Enable slow query logging by setting {log_slow_queries} to 'ON'. This will help troubleshooting badly performing queries.","justification":"log_slow_queries is set to 'OFF'"},{"name":"Query caching method","precondition":"!fired('Query cache disabled')","formula":"Questions \/ Uptime","test":"value > 100","issue":"Suboptimal caching method.","recommendation":"You are using the MySQL Query cache with a fairly high traffic database. It might be worth considering to use <a href=\"http:\/\/dev.mysql.com\/doc\/refman\/5.5\/en\/ha-memcached.html\">memcached<\/a> instead of the MySQL Query cache, especially if you have multiple slaves.","justification":"The query cache is enabled and the server receives %d queries per second. This rule fires if there is more than 100 queries per second. | round(value,1)"},{"name":"Query cache efficiency (%)","precondition":"!PMA_DRIZZLE && Com_select + Qcache_hits > 0 && !fired('Query cache disabled')","formula":"Qcache_hits \/ (Com_select + Qcache_hits) * 100","test":"value < 20","issue":"Query cache not running efficiently, it has a low hit rate.","recommendation":"Consider increasing {query_cache_limit}.","justification":"The current query cache hit rate of %s% is below 20% | round(value,1)"},{"name":"Query Cache usage","precondition":"!fired('Query cache disabled') && !PMA_DRIZZLE","formula":"100 - Qcache_free_memory \/ query_cache_size * 100","test":"value < 80","issue":"Less than 80% of the query cache is being utilized.","recommendation":"This might be caused by {query_cache_limit} being too low. Flushing the query cache might help as well.","justification":"The current ratio of free query cache memory to total query cache size is %s%. It should be above 80% | round(value,1)"},{"name":"Query cache fragmentation","precondition":"!fired('Query cache disabled') && !PMA_DRIZZLE","formula":"Qcache_free_blocks \/ (Qcache_total_blocks \/ 2) * 100","test":"value > 20","issue":"The query cache is considerably fragmented.","recommendation":"Severe fragmentation is likely to (further) increase Qcache_lowmem_prunes. This might be caused by many Query cache low memory prunes due to {query_cache_size} being too small. For a immediate but short lived fix you can flush the query cache (might lock the query cache for a long time). Carefully adjusting {query_cache_min_res_unit} to a lower value might help too, e.g. you can set it to the average size of your queries in the cache using this formula: (query_cache_size - qcache_free_memory) \/ qcache_queries_in_cache","justification":"The cache is currently fragmented by %s% , with 100% fragmentation meaning that the query cache is an alternating pattern of free and used blocks. This value should be below 20%. | round(value,1)"},{"name":"Query cache low memory prunes","precondition":"!PMA_DRIZZLE && Qcache_inserts > 0 && !fired('Query cache disabled')","formula":"Qcache_lowmem_prunes \/ Qcache_inserts * 100","test":"value > 0.1","issue":"Cached queries are removed due to low query cache memory from the query cache.","recommendation":"You might want to increase {query_cache_size}, however keep in mind that the overhead of maintaining the cache is likely to increase with its size, so do this in small increments and monitor the results.","justification":"The ratio of removed queries to inserted queries is %s%. The lower this value is, the better (This rules firing limit: 0.1%) | round(value,1)"},{"name":"Query cache max size","precondition":"!fired('Query cache disabled')","formula":"query_cache_size","test":"value > 1024 * 1024 * 128","issue":"The query cache size is above 128 MiB. Big query caches may cause significant overhead that is required to maintain the cache.","recommendation":"Depending on your environment, it might be performance increasing to reduce this value.","justification":"Current query cache size: %s | ADVISOR_formatByteDown(value, 2, 2)"},{"name":"Query cache min result size","precondition":"!fired('Query cache disabled')","formula":"query_cache_limit","test":"value == 1024*1024","issue":"The max size of the result set in the query cache is the default of 1 MiB.","recommendation":"Changing {query_cache_limit} (usually by increasing) may increase efficiency. This variable determines the maximum size a query result may have to be inserted into the query cache. If there are many query results above 1 MiB that are well cacheable (many reads, little writes) then increasing {query_cache_limit} will increase efficiency. Whereas in the case of many query results being above 1 MiB that are not very well cacheable (often invalidated due to table updates) increasing {query_cache_limit} might reduce efficiency.","justification":"query_cache_limit is set to 1 MiB"},{"name":"Percentage of MyISAM key buffer used","precondition":"!PMA_DRIZZLE && key_buffer_size > 0 && !fired('Max % MyISAM key buffer ever used')","formula":"( 1 - Key_blocks_unused * key_cache_block_size \/ key_buffer_size) * 100","test":"value < 95","issue":"MyISAM key buffer (index cache) % used is low.","recommendation":"You may need to decrease the size of {key_buffer_size}, re-examine your tables to see if indexes have been removed, or examine queries and expectations about what indexes are being used.","justification":"% MyISAM key buffer used: %s%, this value should be above 95% | round(value,1)"},{"name":"Thread cache hit rate %","precondition":"!PMA_DRIZZLE && thread_cache_size > 0","formula":"100 - Threads_created \/ Connections","test":"value < 80","issue":"Thread cache is not efficient.","recommendation":"Increase {thread_cache_size}.","justification":"Thread cache hitrate: %s%, this value should be above 80% | round(value,1)"},{"name":"Is InnoDB disabled?","precondition":"!PMA_DRIZZLE && PMA_MYSQL_INT_VERSION < 50600","formula":"have_innodb","test":"value != \"YES\"","issue":"You do not have InnoDB enabled.","recommendation":"InnoDB is usually the better choice for table engines.","justification":"have_innodb is set to 'value'"},{"name":"InnoDB buffer pool size","precondition":"system_memory > 0","formula":"innodb_buffer_pool_size \/ system_memory * 100","test":"value < 60","issue":"Your InnoDB buffer pool is fairly small.","recommendation":"The InnoDB buffer pool has a profound impact on performance for InnoDB tables. Assign all your remaining memory to this buffer. For database servers that use solely InnoDB as storage engine and have no other services (e.g. a web server) running, you may set this as high as 80% of your available memory. If that is not the case, you need to carefully assess the memory consumption of your other services and non-InnoDB-Tables and set this variable accordingly. If it is set too high, your system will start swapping, which decreases performance significantly. See also <a href=\"http:\/\/www.percona.com\/blog\/2007\/11\/03\/choosing-innodb_buffer_pool_size\/\">this article<\/a>","justification":"You are currently using %s% of your memory for the InnoDB buffer pool. This rule fires if you are assigning less than 60%, however this might be perfectly adequate for your system if you don't have much InnoDB tables or other services running on the same machine. | value"}],"errors":[]}}