Conversation
|
[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. DetailsReviewer can indicate their review by submitting an approval review. |
032738e to
50ed174
Compare
|
/run-all-tests |
|
/run-unit-test |
7 similar comments
|
/run-unit-test |
|
/run-unit-test |
|
/run-unit-test |
|
/run-unit-test |
|
/run-unit-test |
|
/run-unit-test |
|
/run-unit-test |
Coverage for changed filesCoverage summaryfull coverage report (for internal network access only) |
b556676 to
b273666
Compare
b273666 to
504b39a
Compare
|
/run-all-tests |
Coverage for changed filesCoverage summaryfull coverage report (for internal network access only) |
|
/run-all-tests |
Coverage for changed filesCoverage summaryfull coverage report (for internal network access only) |
|
/hold |
|
The short value in lock cf may be used when adapting to cloud engine. So this optimization may be not applicable. |
|
@lidezhu: PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What problem does this PR solve?
Issue Number: ref #4728
Problem Summary: For lock cf, we store both it's
TiKVValuefor serialization andDecodedLockCFValuefor lock resolve which is redundant and consume a lot of memory.What is changed and how it works?
Avoid store TiKVValue for lock cf and generating it on the fly.
Check List
Tests
2. update lineitem set L_SUPPKEY=100000 limit 50000000;Before optimize:


After optimize:
The memory consumption peak decreases about 10GB.
Side effects
Documentation
Release note