*: not send tso request when point get with max tso (#11981)#16335
Merged
sre-bot merged 4 commits intopingcap:release-3.0from Apr 14, 2020
Merged
*: not send tso request when point get with max tso (#11981)#16335sre-bot merged 4 commits intopingcap:release-3.0from
sre-bot merged 4 commits intopingcap:release-3.0from
Conversation
Signed-off-by: sre-bot <sre-bot@pingcap.com>
Contributor
Author
|
/run-all-tests |
Contributor
|
/run-all-tests |
1 similar comment
Contributor
|
/run-all-tests |
Member
|
LGTM |
1 similar comment
Contributor
|
LGTM |
tiancaiamao
approved these changes
Apr 14, 2020
Member
|
/merge |
Contributor
Author
|
Your auto merge job has been accepted, waiting for 16175, 16347, 15859 |
Contributor
Author
|
/run-all-tests |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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 #11981 to release-3.0
What problem does this PR solve?
Point get without double read will use maxUint64 as transaction tso. Then no need to send tso request to PD.
This PR will delay to get txn future after try fast point, so it may have a little performance regression in the case of need to get tso from PD. Especially in the situation of point get with double read.
BenchMark
Environment: In my local machine: 1 TiDB, 1 PD, 5 TiKV.
Best case: Point get with max tso
Before
This PR
Worst case: Point get with double read can't use max tso
Before
In this PR
As you can see, since I delay use get txn future, there is a performance regression is this situation.
What is changed and how it works?
Check List
Tests
Code changes