-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Track spill read-back memory in SMJ #22103
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
Open
SubhamSinghal
wants to merge
4
commits into
apache:main
Choose a base branch
from
SubhamSinghal:smj-spill-read-back-memory-accounting
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+260
−16
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
432f5c7
Track spill read-back memory in SMJ
SubhamSinghal bf54239
Merge branch 'main' into smj-spill-read-back-memory-accounting
SubhamSinghal 81be3f9
Use MemoryReservation for memorary tracking
SubhamSinghal 5614862
Merge branch 'main' into smj-spill-read-back-memory-accounting
SubhamSinghal 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
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.
It looks like
spill_read_memis only shrunk after all file reads and allinterleavecalls succeed. Onceself.reservation.grow(batch_mem)succeeds, any later?such as fromFile::open,StreamReader::try_new,next().transpose(), orinterleavecan return early before the shrink happens at line 1651.That leaves the reservation inflated until the stream is dropped, which breaks the grow/shrink accounting invariant on error paths and can leave the memory pool reporting stale reserved memory after a failed poll.
Could we make this temporary read-back reservation scoped/RAII-based, or otherwise guarantee that
shrinkruns on every return path after a successfulgrow?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.
@kosiew Thanks for highlighting this. Switched from manual
grow/shrinkonself.reservationto a scopedMemoryReservationviaself.reservation.new_empty().