Tune Region Performance
This document introduces how to tune Region performance by adjusting the Region size and how to use bucket to optimize concurrent queries when the Region size is large.
TiKV automatically shards bottom-layered data. Data is split into multiple Regions based on the key ranges. When the size of a Region exceeds a threshold, TiKV splits it into two or more Regions.
When processing a large amount of data, TiKV might split too many Regions, which causes more resource consumption and performance regression. For a certain amount of data, the larger the Region size, the fewer the Regions. Since v6.1.0, TiDB supports setting customizing Region size. The default size of a Region is 96 MiB. To reduce the number of Regions, you can adjust Regions to a larger size.
To reduce the performance overhead of many Regions, you can also enable Hibernate Region or
region-split-size to adjust Region size
To adjust the Region size, you can use the
coprocessor.region-split-size configuration item. The recommended sizes are 96 MiB, 128 MiB, or 256 MiB. The larger the
region-split-size value, the more jittery the performance will be. It is NOT recommended to set the Region size over 1 GiB. Avoid setting the size to more than 10 GiB. When TiFlash is used, the Region size should not exceed 256 MiB.
When the Dumpling tool is used, the Region size should not exceed 1 GiB. In this case, you need to reduce the concurrency after increasing the Region size; otherwise, TiDB might run out of memory.
Use bucket to increase concurrency
When Regions are set to a larger size, you need to set
true to increase the query concurrency. When you use this configuration, Regions are divided into buckets. Buckets are smaller ranges within a Region and are used as the unit of concurrent query to improve the scan concurrency. You can control the bucket size using
coprocessor.region-bucket-size. The default value is