-
Notifications
You must be signed in to change notification settings - Fork 2.1k
perf: optimize array_remove for scalar needle #22390
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
+286
−30
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
9b3f32f
Refactor array remove invocation
lyne7-sc 0c787f4
Merge branch 'apache:main' into perf/remove
lyne7-sc 9697c3a
enhance array_remove slt
lyne7-sc a6e6ad1
Merge branch 'main' into perf/remove
lyne7-sc b6023a0
apply suggestions
lyne7-sc 2e7cd40
apply suggestions
lyne7-sc cdb6021
redundant comparisons
lyne7-sc 4805bb7
clean up per review feedback
lyne7-sc 73bca4f
nit
lyne7-sc 48c27bc
Merge branch 'main' into perf/remove
lyne7-sc 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.
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.
I wonder if an approach using
takekernel could provide even more performance gains?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 benchmarked both
takeandfilterkernel approaches against the currentMutableArrayData::extendpath. Overall,MutableArrayDataperforms best — on small lists (size=10) take is faster (~10%), possibly by avoidingMutableArrayDatainitialization overhead, but on medium/large lists (size≥100)MutableArrayDatatends to win decisively (take is 60–170% slower depending on type). For variable-length types (strings), the gap appears to widen further.One possible explanation is that take performs per-index random access for each element, whereas
MutableArrayDatamay instead execute contiguous memcpy operations over memory regions?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.
But, the current benchmarks use 10% needle density (sparse removals / high retention), which is likely the most common case? For dense removal workloads the trade-offs may shift,
takeorfiltercould become competitive when there are fewer contiguous ranges to memcpy.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.
That makes sense, especially as we're operating on list arrays anyway