Legg filene her

SQL upload ( 0 ) x -

Side-relaterte innstillinger Klikk på linjen for å bla til toppen av siden
Tast Ctrl+Enter for å utføre spørring Press Enter to execute query
ascending
descending
Order:
Feilsøk SQL
Antall
Execution order
Time taken
Order by:
Group queries
Ungroup queries
Slå sammen Utvid Show trace Hide trace Count: Tidsbruk:
Bokmerker
Oppdater
Legg til
Ingen bokmerker
Legg til bokmerke
Innstillinger
Restore default values
Slå sammen Utvid Spør igjen Rediger Forklar Profilering Bokmerke Spørringen mislyktes Database: Spørringens tidsforbruk:

Rådgivningssystem

Mulige ytelsesproblemer

Issue:
Oppetid er mindre enn 1 dag, ytelsejustering er kanskje ikke nøyaktig.
Recommendation:
For å ha mer nøyaktige gjennomsnitt anbefales det å la serveren kjøre lenger enn en dag før du kjører denne analysatoren
Justification:
Oppetid er bare 0 dager, 10 timer, 23 minutter og 4 sekunder
Used variable / formula:
Uptime
Test:
value < 86400
Issue:
long_query_time er satt til 10 sekunder eller mer, og derfor blir bare langsomme spørsmål som tar over 10 sekunder logget.
Recommendation:
Det anbefales å sette long_query_time til en lavere verdi, avhengig av miljøet ditt. Vanligvis foreslås en verdi på 1-5 sekunder.
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:
Aktiver treg logglogging ved å sette slow_query_log til "PÅ". Dette vil hjelpe til med å feilsøke spørsmål som har dårlige resultater.
Justification:
slow_query_log is set to '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: 6.96 per sekund
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: 8.37 per sekund, 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: 18.18 per minutt, 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: 6.88 per sekund, 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: 255.55 per sekund, 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: 46.26 per minutt, 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: 13.77 per time, 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: 7.41 per time, this value should be less than 5 per hour
Used variable / formula:
Open_files / Uptime
Test:
value * 60 * 60 > 5
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 24%. 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