Vedä tiedostot tähän

SQL upload ( 0 ) x -

Sivun asetukset Palkin klikkaus vierittää sivun ylös
Suorita kysely painamalla Ctrl+Enter Paina Enter suorittaaksesi kyselyn
nouseva
laskeva
Järjestys:
Etsi virheitä SQL-kyselystä
Laske
Suoritusjärjestys
Aikaa kului
Järjestä mukaan:
Ryhmäkyselyt
Pura ryhmäkyselyt
Paina kokoon Laajenna Näytä seuranta Piilota seuranta Luku: Aikaa kului:
Valinnat
Restore default values
Paina kokoon Laajenna Suorita hakulause uudelleen Muokkaa Selitä Profilointi Kysely epäonnistui Tietokanta: Hakulauseen suoritusaika:

Neuvontajärjestelmä

Mahdollisia suorituskykyongelmia

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:
The uptime is only 0 päivää, 0 tuntia, 3 minuuttia ja 48 sekuntia
Used variable / formula:
Uptime
Test:
value < 86400
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 long_query_time 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.
Used variable / formula:
long_query_time
Test:
value >= 10
Issue:
The slow query log is disabled.
Recommendation:
Enable slow query logging by setting slow_query_log to 'ON'. This will help troubleshooting badly performing queries.
Justification:
slow_query_log is set to 'OFF'
Used variable / formula:
slow_query_log
Test:
value == 'OFF'
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 memcached instead of the MySQL Query cache, especially if you have multiple replicas.
Justification:
The query cache is enabled and the server receives 200 queries per second. This rule fires if there is more than 100 queries per second.
Used variable / formula:
Questions / Uptime
Test:
value > 100
Issue:
Too many sorts are causing temporary tables.
Recommendation:
Consider increasing sort_buffer_size and/or read_rnd_buffer_size, depending on your system memory limits.
Justification:
Temporary tables average: 11.32 minuutissa, this value should be less than 1 per hour.
Used variable / formula:
Sort_merge_passes / Uptime
Test:
value * 60 * 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: 407.08 sekunnissa
Used variable / formula:
Sort_rows / Uptime
Test:
value * 60 >= 1
Issue:
There are too many joins without indexes.
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: 203.31 sekunnissa, 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: 156.18 sekunnissa, 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: 209.16 sekunnissa, 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:
This indicates that many queries are doing full table scans. Add indexes where applicable.
Justification:
Rate of reading next table row: 8188.94 sekunnissa, this value should be less than 1 per hour
Used variable / formula:
Handler_read_rnd_next / Uptime
Test:
value * 60 * 60 > 1
Issue:
Many temporary tables are being written to disk instead of being kept in memory.
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:
Rate of temporary tables being written to disk: 15 minuutissa, this value should be less than 1 per hour
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:
The rate of opening tables is high.
Recommendation:
Opening tables requires disk I/O which is costly. Increasing table_open_cache might avoid this.
Justification:
Opened table rate: 3.13 sekunnissa, this value should be less than 10 per hour
Used variable / formula:
Opened_tables / Uptime
Test:
value*60*60 > 10
Issue:
The rate of opening files is high.
Recommendation:
Consider increasing open_files_limit, and check the error log when restarting after changing open_files_limit.
Justification:
Opened files rate: 2.11 minuutissa, this value should be less than 5 per hour
Used variable / formula:
Open_files / Uptime
Test:
value * 60 * 60 > 5