Home  >  Article  >  Database  >  Learn more about MySQL slow log queries

Learn more about MySQL slow log queries

WBOY
WBOYforward
2022-04-02 13:10:352833browse

This article brings you relevant knowledge about mysql, which mainly introduces the related issues of slow log query, and also includes show profiles to view the specific running time of sql and other related content. I hope Helpful to everyone.

Learn more about MySQL slow log queries

Recommended learning: mysql video tutorial

1. Slow query log concept

For SQL For index optimization issues, we will use explain to analyze SQL statements. But real enterprise-level projects have thousands of SQL statements, and it is impossible for us to analyze them one by one from scratch. Where can we get those long-running, performance-consuming SQL? ?

We can open the slow query log:

Estimate a time limit (20ms, 100ms) based on the specific business and concurrency, and start the business after setting it. After the stress test, open the slow query log, and you will see the SQL that exceeds the execution time, and then use explain to analyze these time-consuming SQL statements.

The steps are as follows:

  • Open Slow query log switchslow_query_log

  • Set a reasonable slow query time limit that is acceptable to the business

  • Stress test execution Various businesses

  • Check the slow query log and find out all the SQL statements that take time to execute

  • Use explain to analyze these time-consuming SQL statements , thereby targeted optimization

MySQL can set up slow query logs. When the execution time of SQL exceeds the time we set, these SQLs will be recorded in the slow query log, and then We check the logs and use explain to analyze the execution plans of these SQLs to determine why the efficiency is low. Is it because the index is not used? Or is there something wrong with the creation of the index itself? Or the index is used, but because the amount of data in the table is too large, it takes a long time. At this time, we can divide the table into multiple small tables, etc.

The parameters related to the slow query log are as follows:
(Many global switches defined by MySQL are stored in global variables, which can be viewed with show/set variables Or set the value of global variables)

Learn more about MySQL slow log queries
The slow query log switch is turned off by default
The path of the slow query log: the default is /var/lib/mysql/

The slow query log records logs containing all SQL statements whose execution time exceeds the value set by the parameter long_query_time (unit: seconds). You can view it with the command on MySQL, as follows:

Learn more about MySQL slow log queries
This value can be modified:

Learn more about MySQL slow log queries

2. Slow query log practice

1. Turn on the slow query log switch slow_query_log

Learn more about MySQL slow log queries

When the slow query log switch is turned on, an error message indicates that slow_query_log is a global variable (there are also variables that only affect the current session, such as: long_query_time, profiling ), the modification will affect all sessions, that is, all clients accessing the current MySQL server.
Learn more about MySQL slow log queries
Turning on the slow query log switch was successful!

2. Set a reasonable and business-acceptable slow query time upper limit long_query_time

Learn more about MySQL slow log queries
View another session

Learn more about MySQL slow log queries
It was found that the default value is still 10s, so long_query_time only affects the current session

3. Stress test to execute various services

Learn more about MySQL slow log queries
Already Exceeds the long_query_time=0.1s we set

4. Check the slow query log

Path: /var/lib/mysql/
Learn more about MySQL slow log queries
Learn more about MySQL slow log queries

5. Use explain to analyze these time-consuming SQL statements to optimize them accordingly

Learn more about MySQL slow log queries
Searched the entire table and scanned the entire primary key index tree Read it again.

We should add an index to the password, and then remember that the password is in string format, because if type conversion is involved, the index cannot be used

3. Show profiles to view the specific running time of SQL

MySQL generally only displays the time to two decimal places
Learn more about MySQL slow log queries
Turn on the profiling switch to display more detailed time

Learn more about MySQL slow log queries
No error is reported, indicating that the profiling variable only Affects the current session

Learn more about MySQL slow log queries

Recommended learning: mysql video tutorial

The above is the detailed content of Learn more about MySQL slow log queries. For more information, please follow other related articles on the PHP Chinese website!

Statement:
This article is reproduced at:csdn.net. If there is any infringement, please contact admin@php.cn delete