Skip to content
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

Let PointGet be a choice of DataSource's PhysicalPlan. #14044

Closed
winoros opened this issue Dec 12, 2019 · 1 comment · Fixed by #14775
Closed

Let PointGet be a choice of DataSource's PhysicalPlan. #14044

winoros opened this issue Dec 12, 2019 · 1 comment · Fixed by #14775
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. sig/execution SIG execution sig/planner SIG: Planner type/performance

Comments

@winoros
Copy link
Member

winoros commented Dec 12, 2019

Feature Request

There're two api to access data in TiKV. One is kv's Get/BatchGet, the other is coprocessor. Get/BatchGet is lighter than coprocessor. There's no other calculation(like filter or aggregate). The Get will have significant stronger performance compared with coprocessor.

So there is a need to make the PointGet as a choice of DataSource's Physical Plan.

@zz-jason
Copy link
Member

zz-jason commented Feb 5, 2020

The Get will have significant stronger performance compared with coprocessor.

Do we have some benchmark result to quantify the performance difference?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. sig/execution SIG execution sig/planner SIG: Planner type/performance
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants