-
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
control chunk size to optimize query latency and resource consumption #6489
Labels
Comments
zz-jason
added
the
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
label
May 7, 2018
After this PR #8994, we are able to set required chunk size for each executor. |
zz-jason
changed the title
we may need to grow batch size from a small value to
control chunk size to optimize query latency and resource consumption
Mar 26, 2019
tidb_max_chunk_size
zz-jason
removed
the
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
label
Mar 26, 2019
zz-jason
added
type/enhancement
The issue or PR belongs to an enhancement.
sig/execution
SIG execution
labels
Mar 26, 2019
Closed
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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 1024The text was updated successfully, but these errors were encountered: