# Identifying Hotspots Using the `Dashboard` - `Key Visualizer` - Cont'd

![`smart`](MonitorHotspot03_aa_001_20231020.png)
![`smart`](TiKVRegionHotSpotInsertionAutoIncrement_en_001_20230906.png)

------------------------------------------------------------------------------
Contrary to the `k_1` index, the `Key Visualizer` of the `sbtest1` table in the `sbtest` database (with brightness indicating `Write (bytes)`) reveals that during a continuous time period, there is consistently a TiKV Region of high brightness at every instant. Moreover, as time advances, this TiKV Region of high brightness shifts.

Recall that the `sbtest1` table in the `sbtest` database is a table with clustered index for primary key, and there are concurrent data insertions from multiple sessions. Additionally, the primary key column has the `AUTO_INCREMENT` property. At any given time, data can only be written to one TiKV Region, which means that only one block is currently receiving new data. When this TiKV Region reaches its maximum capacity, it splits, and the TiDB servers start writing to the next available TiKV Region. As a result, the next TiKV Region becomes active again, while the previous region remains mostly inactive (cold).

This is the reason why, at a specific point in the slide, only one block appears to be the brightest, and the TiKV Region that was previously the brightest (hot) quickly becomes dark (cold). In this diagram, we observe that during this write operation, the majority of write traffic is concentrated in one TiKV Region at any given time. Each instant has a hotspot, however, the specific hotspot TiKV Region varies from moment to moment.