-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Increase batch size #8388
Closed
Closed
Increase batch size #8388
Conversation
This file contains 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
github-actions
bot
added
core
Core DataFusion crate
sqllogictest
SQL Logic Tests (.slt)
labels
Dec 1, 2023
Here are my results at sf10 on a 24 core Threadripper, showing a 7% slowdown overall.
|
Wow, interesting difference! |
Marking as a draft to make it clear this PR isn't waiting on review (I don't think) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which issue does this PR close?
Closes #6916
Rationale for this change
We should have some more optimal defaults.
32K seems for this machine relatively optimal. Increasing to 64K does further improve performance on some queries, but also slows down a couple.
Tested on apple m1 (10 core)
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?