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

control chunk size to optimize query latency and resource consumption #6489

Open
zz-jason opened this issue May 7, 2018 · 1 comment

Comments

@zz-jason
Copy link
Member

commented May 7, 2018

Currently we use 1024 as the default batch size, but some OLTP workloads may not need to read or return very much rows, thus we need a small batch size to reduce the overhead of making a big slice of size 1024

@zz-jason zz-jason added the help wanted label May 7, 2018

@zz-jason

This comment has been minimized.

Copy link
Member Author

commented Jan 13, 2019

After this PR #8994, we are able to set required chunk size for each executor.

@zz-jason zz-jason changed the title we may need to grow batch size from a small value to `tidb_max_chunk_size` control chunk size to optimize query latency and resource consumption Mar 26, 2019

@zz-jason zz-jason removed the help wanted label Mar 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.