# Slow Sql Analysis Conclusions

+ Analysis conclusion:
  + The execution plan of the SQL statement has not changed (no deviation)
  + The waiting time for SQL statements is mainly concentrated on the coprocessor on the TiKV side, which scans a large number of keys
+ Further confirm the direction:
  + Scan keys by the coprocessor on the TiKV side
  + Business acknowledges data growth
------------------------------------------------------------
The execution plan of SQL is not skewed
Waiting time for SQL: Mainly concentrated on the TiKV side coprocessor, where SQL scans a large number of keys and leaves them to be checked
- The amount of data in the target table report_interact_detail corresponding to Slow Query SQL is constantly increasing, and the increment of the data in the table needs to be checked
  - Order by winning_create_time DESC is used in SQL and index scans use a single-column index on the create_time field