store/copr: revert pr/35975, do not reduce concurrency for keep order coprocessor request (#55141) #55640
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.
This is an automated cherry-pick of #55141
What problem does this PR solve?
Issue Number: close #54969
Problem Summary:
What changed and how does it work?
In the past, #35975 reduce coprocessor concurrency to 2 for the keep order query.
But recently we meet an oncall case that the change cause performance regression.
Balance the memory usage and concurrency is a difficult job,
we need more tests and expirements to reach the conclusion.Currently we can simply set TiFlash to not reduce concurrency, when a user using TiFlash, the tidb memory usage would not be a top concern (their hardware must be better).Check List
Tests
See comments below
One line change, just revert part of the previous optimization.
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.