Letakkan berkas disini

SQL upload ( 0 ) x -

Pengaturan Terkait dengan Halaman Klik 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:

Sistem penasihat

Isu kinerja yang mungkin

Issue:
Uptime kurang dari 1 hari, tuning kinerja mungkin tidak akurat.
Recommendation:
Untuk mendapatkan rata-rata yang lebih akurat, disarankan untuk membiarkan server berjalan lebih lama dari satu hari sebelum menjalankan penganalisis ini
Justification:
Uptime hanya 0 hari, 15 jam, 0 menit dan 19 detik
Used variable / formula:
Uptime
Test:
value < 86400
Issue:
long_query_time disetel ke 10 detik atau lebih, jadi hanya kueri lambat yang membutuhkan waktu di atas 10 detik yang dicatat.
Recommendation:
Disarankan untuk mengatur long_query_time ke nilai yang lebih rendah, tergantung pada lingkungan Anda. Disarankan biasanya nilai dari 1-5 detik.
Justification:
long_query_time saat ini disetel menjadi 10 detik.
Used variable / formula:
long_query_time
Test:
value >= 10
Issue:
Log kueri yang lambat dinonaktifkan.
Recommendation:
Aktifkan logging query dengan menetapkan slow_query_log ke 'ON'. Ini akan membantu pemecahan masalah pada query yang bekerja buruk.
Justification:
slow_query_log disetel ke 'OFF'
Used variable / formula:
slow_query_log
Test:
value == 'OFF'
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: 12.79 per menit
Used variable / formula:
Sort_rows / Uptime
Test:
value * 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: 44.87 per menit, this value should be less than 1 per hour
Used variable / formula:
(Select_range_check + Select_scan + Select_full_join) / 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: 1.83 per menit, this value should be less than 1 per hour
Used variable / formula:
Handler_read_first / 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: 12.56 per menit, this value should be less than 1 per hour
Used variable / formula:
Handler_read_rnd / Uptime
Test:
value * 60 * 60 > 1
Issue:
The rate of reading the next table row is high.
Recommendation:
Hal ini menunjukkan bahwa banyak kueri yang melakukan scan tabel secara menyeluruh. Menambahkan indeks dimana memungkinkan.
Justification:
Tingkat (kecepatan) membaca baris tabel selanjutnya: 16.76 per detik, nilai ini seharusnya kurang dari 1 per jam
Used variable / formula:
Handler_read_rnd_next / Uptime
Test:
value * 60 * 60 > 1
Issue:
Banyak tabel sementara yang ditulis ke disk daripada disimpan di memori.
Recommendation:
Increasing max_heap_table_size and tmp_table_size 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 MySQL Documentation
Justification:
Tingkat pembuatan tabel temporer ke diska: 9.99 per menit, nilai ini hasul kurang dari 1 per jam
Used variable / formula:
Created_tmp_disk_tables / Uptime
Test:
value * 60 * 60 > 1
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:
max % MyISAM key buffer ever used: 0%, this value should be above 95%
Used variable / formula:
Key_blocks_used * key_cache_block_size / key_buffer_size * 100
Test:
value < 95
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 4%. It should be above 80%
Used variable / formula:
100 - Qcache_free_memory / query_cache_size * 100
Test:
value < 80
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
Used variable / formula:
query_cache_limit
Test:
value == 1024*1024