# Case Study Solution (A)

+ Split a hot spot:
  + `set config tikv split.qps-threshold=3000` 
  + `set config tikv split.byte-threshold=30` 
+ Applicable scenario for above solution:
  + There is not much room for SQL statement optimization
  + The target table has a large amount of data, and it takes unacceptable time to create a new index
  + SQL statement optimization requires design business transformation

------------------------------------------------------------

If you encounter the phenomenon that your production environment is being affected by read hotspots, you can try to break up read hotspots in the following ways:

- Load Base Split
This feature was introduced in TiKV version 4.0 to address hot issues caused by uneven distribution of region access, such as full table scans of small tables. Automatically split regions based on Region. Statistically identify regions where read traffic continues to exceed the threshold for 10s, and split these regions at appropriate locations. When selecting locations to split, try to balance visits across the two regions after the split as possible, and avoid visits across regions as Region as possible.
The control parameter is split.qps-threshold, the default value is 3000. Two adjustment methods are recommended, 1: