# Before Top Sql

![left](./student-guide/diagram/TopSQLBefore01_en_001_20220515.png)

------------------------------------------------------------
Before TiDB 6.0, when we encountered a sudden increase in CPU usage of a TiKV instance, if we wanted to locate the problem SQL, there were only 2 tools, Slow Query or SQL Queries, but the problem was that both tools were for the entire TiDB cluster and were not targeted at TiDB Server or TiKV instances are used to distinguish them, and they do not directly count the CPU consumption of certain types of SQL.
As a result, there are often scenario where there is a clear suspicion of a few pieces of SQL but there is not enough evidence, or there is no way to face an increase in CPU load.