Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Shrink containers if their capacity isn't needed #405

Closed
wants to merge 1 commit into from
Closed

Shrink containers if their capacity isn't needed #405

wants to merge 1 commit into from

Conversation

antiguru
Copy link
Member

This eagerly releases memory after retracting large amount of data, without having to wait for another operation to happen.

@antiguru
Shrink containers if their capacity isn't needed
43b21f2 
This eagerly releases memory after retracting large amount of data, without
having to wait for another operation to happen.

Signed-off-by: Moritz Hoffmann <[email protected]>
@antiguru
Copy link
Member Author

With TimelyDataflow/timely-dataflow#530, we could shrink the Columnation-based variant, too.

@antiguru
Copy link
Member Author

Not needed anymore with ord_neu. In addition, this only releases virtual memory, so it might need more memory than before because it needs to copy into a new allocation.

@antiguru antiguru closed this Dec 20, 2023
@antiguru antiguru deleted the batch_shrinking branch December 20, 2023 19:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@frankmcsherry frankmcsherry Awaiting requested review from frankmcsherry

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@antiguru