Shulou(Shulou.com)06/01 Report--

First, view slow queries

If slow queries are confirmed, then slow queries should be measured instead of measuring the overall server performance to capture MySQL queries to slow log files. You can capture all queries by setting long_query_time to 0, and the query response time is measured in microseconds. However, if you record it in a table in the database, it not only has a great impact on performance, but also can only be accurate to seconds.

Second, locate and optimize subtasks

Some subtasks that run infrequently or very short, such as a SQL statement, have little impact on the overall response time, so there is no need to delve into it. However, we should also pay attention to whether the execution time of these subtasks which seem to have little impact on locating the problem task is affected.

Third, performance analysis

1. Measure the time spent on tasks. 2. Count and sort the results. Assign important tasks to the front. 3. Group tasks into groups. 4. Believe only the average is very dangerous.

IV. Server system level

Set up a scheduled task to grab a summary of top performance-related parameters (CPU, memory, IO read and write performance, etc.), and analyze the system-level load of the time period in which the problem occurs.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.