restore: merge small ranges (#578) #655
Conversation
Signed-off-by: ti-srebot <[email protected]>
|
@overvenus please fix merge conflicts |
Signed-off-by: Neil Shen <[email protected]>
|
/run-all-tests |
…) (pingcap#658) * cherry pick pingcap#468 to release-4.0 Signed-off-by: ti-srebot <[email protected]>
|
/run-all-tests |
overvenus
added
type/4.0-cherry-pick
component/restore
type/performance
and removed
cherry-pick
labels
Signed-off-by: Neil Shen <[email protected]>
|
@3pointer PTAL |
Signed-off-by: Neil Shen <[email protected]>
|
@overvenus Please resolve the conflict. |
Signed-off-by: Neil Shen <[email protected]>
|
/run-integration-tests |
2 similar comments
|
/run-integration-tests |
|
/run-integration-tests |
|
/run-integration-tests |
1 similar comment
|
/run-integration-tests |
|
/LGTM |
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
|
/merge |
|
This pull request has been accepted and is ready to merge. Commit hash: 9e80ad5
|
|
/run-integration-tests |
cherry-pick #578 to release-4.0
What problem does this PR solve?
Speed up restore by merging small range to reduce split and scatter.
What is changed and how it works?
Merge adjacent ranges that total_bytes is less 96MB or total_kv is less than 960000.
Check List
Tests
Side effects
Breaking backward compatibilityRelease Note