storage: Abort vector index building as soon as possible #9443
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Issue Number: close #9032
Problem Summary:
What is changed and how it works?
Pick https://github.com/tidbcloud/tiflash-cse/pull/232, https://github.com/tidbcloud/tiflash-cse/pull/240 and https://github.com/tidbcloud/tiflash-cse/pull/270
TODO: In this PR, index build is cancelled after segment stable is invalid, e.g. after applyMergeDelta. Maybe we can do it as soon as possible, e.g. when prepareMergeDelta?
Benchmark @ M1 Pro:
efSearch=64, TopK=10: 107826 ns
efSearch=16, TopK=10: 63858 ns
Check List
Tests
Run VectorDBBench, and we can see that during the data loading process actually all vector index build will be cancelled:
Side effects
Documentation
Release note