Skip to content

Add optimized batch update of hotspot indexes to release-6.0.0-dmr #8671

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ti-chi-bot merged 6 commits into from
Jun 7, 2022
Merged

Add optimized batch update of hotspot indexes to release-6.0.0-dmr #8671

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
f87242c
add Optimized batch update of hotspot indexes
Oreoxmt May 18, 2022
fa57436
Apply suggestions from code review
Oreoxmt May 20, 2022
b089981
update Optimization of hotspot index
Oreoxmt May 23, 2022
666395e
Apply suggestions from code review
Oreoxmt May 24, 2022
7db3c80
Apply suggestions from code review
Oreoxmt May 25, 2022
4ad8411
Apply suggestions from code review
Oreoxmt May 25, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions releases/release-6.0.0-dmr.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,6 +111,12 @@ TiDB v6.0.0 is a DMR, and its version is 6.0.0-DMR.

[User document](/functions-and-operators/expressions-pushed-down.md#add-to-the-blocklist), [#30738](https://github.com/pingcap/tidb/issues/30738)

- Optimization of hotspot index

Writing monotonically increasing data in batches to the secondary index causes an index hotspot and affects the overall write throughput. Since v6.0.0, TiDB supports scattering the index hotspot using the `tidb_shard` function to improve the write performance. Currently, `tidb_shard` only takes effect on the unique secondary index. This application-friendly solution does not require modifying the original query conditions. You can use this solution in the scenarios of high write throughput, point queries, and batch point queries. Note that using the data that has been scattered by range queries in the application might cause a performance regression. Therefore, do not use this function in such cases without verification.

[User document](/functions-and-operators/tidb-functions.md#tidb_shard), [#31040](https://github.com/pingcap/tidb/issues/31040)

- Support dynamic pruning mode for partitioned tables in TiFlash MPP engine (experimental)

In this mode, TiDB can read and compute the data on partitioned tables using the MPP engine of TiFlash, which greatly improves the query performance of partitioned tables.
Expand Down