# Before Top SQL

![`smart`](TopSQLBefore01_aa_003_20220515.png)

-------------------------------------------------------------
Before TiDB v6.0, when we encountered a sudden increase in the CPU usage of a TiKV instance, if we wanted to locate the problem SQL statement, we could only use the two tools Slow Query or SQL Statements, but the problem was that these two tools were for the entire TiDB cluster, without distinguishing between TiDB server or TiKV instance, and without statistics of CPU consumption of a certain type of SQL statement.