-
Notifications
You must be signed in to change notification settings - Fork 2.1k
bench: first_last remove noisy benchmarks, add update_batch #21487
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
Merged
+172
−75
Merged
Changes from 6 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
97beaa1
Remove noisy benchmarks for first_last
theirix fbef405
Measure using iter_custom
theirix f6216a3
Add benches for update_batch, merge_batch
theirix f1e327e
Prepopulate with worst-case ordering
theirix 5d98dc0
Fixup bench name
theirix 4f29c61
Add bench for Accumulator
theirix 1a58f05
Run update/merge multiple times for each accumulator
theirix File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
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.
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.
Why are we creating more than one accumulator?
I think the important benchmark is a single accumuatlor and then merge multiple batches per iteration. This seems like it merges one batch per iteration across multiple accumulators?
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.
It's for scaling runs. One run of evaluate / update_bench / merge_bench is diminishingly fast, so multiple accumulators are created just to run a benchmark function on them. We cannot just run 1000 iterations for
evaluate/...since it mutates the state.However, for update_bench / merge_bench we can merge multiple batches for one bench run - I'll try this
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.
I've implemented these ideas, but the new update/merge benchmarks are still quite noisy, fluctuating by up to 10%. Still, the effect of UDF optimisation, like in the original PR, is clearly visible.