[store/tikv] support batch coprocessor for TiFlash (#16030) #16226
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.
cherry-pick #16030 to release-4.0
What problem does this PR solve?
Send batch coprocessor request which contains multiple regions to TiFlash Engine
Problem Summary:
What is changed and how it works?
What's Changed:
In old time, tidb sends requests to tiflash in the way of
per region per requests
. But most queries that send to tiflash will involves massive regions, which have huge overhead. And tiflash cannot decide the concurrency of runtime by itself.How it Works:
coprocessor.BatchRequest
.Related changes
we update kvproto pingcap/kvproto#586
####Side effects
We use a system variable tidb_allow_batch_cop to switch the batch cop mode. It has no effect on requests that send to tikv. For TiFlash, it only effects queries like 'Aggregation' and 'TopN' by default. In conclusion, its risk is very low.
**TPCH 50G Benchmark result **
Release note