-
Notifications
You must be signed in to change notification settings - Fork 26.1k
Releasing child request builder memory from BulkRequestBuilder #105194
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
masseyke
merged 6 commits into
elastic:main
from
masseyke:release-bulk-request-builder-memory
Feb 7, 2024
+37
−9
Merged
Changes from 3 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
cdc4dd4
Releasing request memory from BulkRequestBuilder
masseyke 3613875
Adding a couple of test assertions
masseyke 80e8952
Adding a runtime assertion
masseyke 40a280c
using an ArrayDeque for better runtime performance
masseyke bbacde4
Merge branch 'main' into release-bulk-request-builder-memory
masseyke 289152d
simplifying for loop
masseyke 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
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
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 believe removing items one-by-one from an
ArrayListiterator is an O(N²) operation because each.remove()call has to shuffle all the remaining elements down by one. Maybe just set them tonullinstead and then clear the list at the end? Or maybe use a queue instead?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.
Yeah
ArrayDequeis essentially anArrayListwith a moveable head so it'd work better here.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 think you can avoid explicitly using the iterator and just clear the
ArrayListafter iterating over it.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.
Waiting until the end and then clearing all the builders still has the 2x peak memory usage problem that we're trying to solve.
Uh oh!
There was an error while loading. Please reload this page.
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.
Good point. I'll rework this. According to the ArrayDeque javadocs
So it might not be the way to go either. Maybe null and clear (
or new list -- seems like i've seen clear be slow for large lists) is the way to go.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 you wouldn't need to use any of those O(N) operations with
ArrayDeque, you'd be callingpollFirst()which is definitely O(1).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.
Oops, right. :)