# Locate Problematic Sql Statements 

+ High-frequency statements are the focus of optimization

![left](./student-guide/diagram/20-Quickly-locate-problematic-SQL-01-01.png)

------------------------------------------------------------
Optimization of high-frequency statements is a very important part of database system optimization

We can see the statements that consume a lot of resources in the PD dashboard. The resource consumption here may be viewed from multiple dimensions. For example, a single statement executes quickly, but because of frequent multiple executions, the total execution time is very long. Or a single statement does not take much memory, but because it is executed multiple times frequently, the overall memory consumption is higher.

On the page, we can click on the corresponding sql to see the detailed information. For example, we can see the full text of the SQL, the complete execution plan, and the basic information of the SQL, execution time, coprocessor read, transaction, etc.

For such statements, such high-frequency sql, there may not be any performance problems one by one, but these statements are the focus of our optimization.

Is it possible to optimize the statement by creating an index, and if an index exists, whether it is possible to use the point get operator. If the data in the table is relatively static and has not changed too much, can you consider cache the results.

The optimization of these high-frequency statements is a very important part of database system optimization.