-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
table: use evalBuffer to improve performance of locatePartition (#18818) #19647
table: use evalBuffer to improve performance of locatePartition (#18818) #19647
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
/run-all-tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@imtbkcat please resolve conflict and fix CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/merge |
/run-all-tests |
@ti-srebot merge failed. |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@ti-srebot merge failed. |
/merge |
/run-all-tests |
cherry-pick #18818 to release-3.0
What problem does this PR solve?
Issue Number: close #16667
Problem Summary:
MutRowFromDatums
is so heavy that causelocatePartition
performance worse than expected. Especially inLOAD DATA
, partition table need nearly twice time than general table.What is changed and how it works?
What's Changed:
partition by hash(col)
orpartition by range(col)
, get integer value directly.evalBuffer
to avoidMutRowFromDatums
repeatly.How it Works:
This two method will avoid using
MutRowFromDatums
many times. improve the write performance of partition table.Related changes
Check List
Tests
Side effects
Release note