Analyzing the MySQL Slow Query Log to Find Performance Bottlenecks
Turn on MySQL slow query logs and analyze locationable performance issues. 1. Edit the configuration file or dynamically set slow_query_log and long_query_time; 2. The log contains key fields such as Query_time, Lock_time, Rows_examined to assist in judging efficiency bottlenecks; 3. Use mysqldumpslow or pt-query-digest tools to efficiently analyze logs; 4. Optimization suggestions include adding indexes, avoiding SELECT *, splitting complex queries, etc. For example, adding an index to user_id can significantly reduce the number of scanned rows and improve query efficiency.
MySQL's slow query log is an important tool for troubleshooting performance issues. If you find that the database response is slow, or some page loading time increases significantly, turning on and analyzing slow query logs can often quickly locate the problem.

Turn on slow query log
First, make sure that the slow query log is enabled and a suitable definition of "slow" is set. By default, this value is 1 second, but you can adjust it according to actual needs:

- Edit
my.cnf
ormy.ini
file:slow_query_log = 1 slow_query_log_file = /var/log/mysql/mysql-slow.log long_query_time = 0.5
It can also be dynamically set through SQL:
SET GLOBAL slow_query_log = 'ON'; SET GLOBAL long_query_time = 0.5;
Note: After modifying the parameters, you may need to reconnect or refresh the session to take effect.

Analyze slow query log content
Each line of the record in the log file contains execution time, lock time, return number of rows, scan number of rows, and actual execution of SQL statements. for example:
# Query_time: 2.34 Lock_time: 0.00 Rows_sent: 10 Rows_examined: 100000 SELECT * FROM orders WHERE user_id = 123;
Although the above SQL only returns 10 data, it scans 100,000 rows, indicating that it is likely that the index is missing or the query method is not efficient enough.
Several common key fields:
-
Query_time
: The time taken in the entire query (seconds) -
Lock_time
: the time to wait for the lock -
Rows_examined
: Number of rows scanned -
Rows_sent
: The number of rows sent to the client
If Rows_examined
is much larger than Rows_sent
, then you need to consider optimizing the index or query structure.
Recommended commonly used analysis tools
Manual log viewing is inefficient, and some tools can be used to help analyze:
mysqldumpslow : MySQL comes with command line tool, which can count and summarize slow queries.
mysqldumpslow -s at -t 10 /var/log/mysql/mysql-slow.log
The above command will sort by average time and list the top 10 slowest queries.
pt-query-digest : A tool in Percona Toolkit, which is more powerful and supports more complex aggregation and analysis.
pt-query-digest /var/log/mysql/mysql-slow.log > report.txt
These tools can help you find out which SQLs appear frequently and consume more resources, so as to prioritize optimization.
Common optimization suggestions
Once you find the slow queries, the next step is to optimize them. Here are some common practices:
- Index fields that are frequently queried, especially fields in
WHERE
andJOIN
conditions - Avoid using
SELECT *
and select only necessary fields - Use
EXPLAIN
to view the execution plan and confirm whether the index is hit - Reasonably split complex queries to avoid long-term use of resources in large queries
- Do table analysis regularly (
ANALYZE TABLE
) to keep statistical information accurate
For example, the above mentioned SELECT * FROM orders WHERE user_id = 123;
if no index is established on user_id
, you can greatly improve performance by adding indexes:
ALTER TABLE orders ADD INDEX idx_user_id (user_id);
When this is executed again, the number of scanned rows may drop from tens of thousands to tens of dozens, which is very obvious.
Basically that's it. It is not particularly difficult to analyze slow query logs, but it is indeed easy to ignore some details, such as whether the index actually works, whether the execution plan has changed, etc. As long as you insist on regular inspections, you can promptly discover potential problems SQL to avoid performance deterioration.
The above is the detailed content of Analyzing the MySQL Slow Query Log to Find Performance Bottlenecks. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











MySQL query performance optimization needs to start from the core points, including rational use of indexes, optimization of SQL statements, table structure design and partitioning strategies, and utilization of cache and monitoring tools. 1. Use indexes reasonably: Create indexes on commonly used query fields, avoid full table scanning, pay attention to the combined index order, do not add indexes in low selective fields, and avoid redundant indexes. 2. Optimize SQL queries: Avoid SELECT*, do not use functions in WHERE, reduce subquery nesting, and optimize paging query methods. 3. Table structure design and partitioning: select paradigm or anti-paradigm according to read and write scenarios, select appropriate field types, clean data regularly, and consider horizontal tables to divide tables or partition by time. 4. Utilize cache and monitoring: Use Redis cache to reduce database pressure and enable slow query

CTEs are a feature introduced by MySQL8.0 to improve the readability and maintenance of complex queries. 1. CTE is a temporary result set, which is only valid in the current query, has a clear structure, and supports duplicate references; 2. Compared with subqueries, CTE is more readable, reusable and supports recursion; 3. Recursive CTE can process hierarchical data, such as organizational structure, which needs to include initial query and recursion parts; 4. Use suggestions include avoiding abuse, naming specifications, paying attention to performance and debugging methods.

The security of remote access to MySQL can be guaranteed by restricting permissions, encrypting communications, and regular audits. 1. Set a strong password and enable SSL encryption. Force-ssl-mode=REQUIRED when connecting to the client; 2. Restrict access to IP and user rights, create a dedicated account and grant the minimum necessary permissions, and disable root remote login; 3. Configure firewall rules, close unnecessary ports, and use springboard machines or SSH tunnels to enhance access control; 4. Enable logging and regularly audit connection behavior, use monitoring tools to detect abnormal activities in a timely manner to ensure database security.

WhensettingupMySQLtables,choosingtherightdatatypesiscrucialforefficiencyandscalability.1)Understandthedataeachcolumnwillstore—numbers,text,dates,orflags—andchooseaccordingly.2)UseCHARforfixed-lengthdatalikecountrycodesandVARCHARforvariable-lengthdata

1. The first choice for the Laravel MySQL Vue/React combination in the PHP development question and answer community is the first choice for Laravel MySQL Vue/React combination, due to its maturity in the ecosystem and high development efficiency; 2. High performance requires dependence on cache (Redis), database optimization, CDN and asynchronous queues; 3. Security must be done with input filtering, CSRF protection, HTTPS, password encryption and permission control; 4. Money optional advertising, member subscription, rewards, commissions, knowledge payment and other models, the core is to match community tone and user needs.

CTE is a temporary result set in MySQL used to simplify complex queries. It can be referenced multiple times in the current query, improving code readability and maintenance. For example, when looking for the latest orders for each user in the orders table, you can first obtain the latest order date for each user through the CTE, and then associate it with the original table to obtain the complete record. Compared with subqueries, the CTE structure is clearer and the logic is easier to debug. Usage tips include explicit alias, concatenating multiple CTEs, and processing tree data with recursive CTEs. Mastering CTE can make SQL more elegant and efficient.

Temporary tables are tables with limited scope, and memory tables are tables with different storage methods. Temporary tables are visible in the current session and are automatically deleted after the connection is disconnected. Various storage engines can be used, which are suitable for saving intermediate results and avoiding repeated calculations; 1. Temporary tables support indexing, and multiple sessions can create tables with the same name without affecting each other; 2. The memory table uses the MEMORY engine, and the data is stored in memory, and the restart is lost, which is suitable for cache small data sets with high frequency access; 3. The memory table supports hash indexing, and does not support BLOB and TEXT types, so you need to pay attention to memory usage; 4. The life cycle of the temporary table is limited to the current session, and the memory table is shared by all connections. When choosing, it should be decided based on whether the data is private, whether high-speed access is required and whether it can tolerate loss.

The steps for setting MySQL semi-synchronous replication are as follows: 1. Confirm the version supports and load the plug-in; 2. Turn on and enable semi-synchronous mode; 3. Check the status and operation status; 4. Pay attention to timeout settings, multi-slave library configuration and master-slave switching processing. It is necessary to ensure that MySQL 5.5 and above versions are installed, rpl_semi_sync_master and rpl_semi_sync_slave plugins, enable corresponding parameters in the master and slave library, and configure automatic loading in my.cnf, restart the service after the settings are completed, check the status through SHOWSTATUS, reasonably adjust the timeout time and monitor the plug-in operation.
