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

Explore: Alter handling of free batches. #728

Open

mjp41 opened this issue Jan 7, 2025 · 0 comments

Member

mjp41 commented Jan 7, 2025

In #724, we added a limit to how many remote frees could be processed in one go. This should improve general performance of batched frees.

As part of this PR, there was a discussion about taking this further. This issue is raised to not lose that discussion.

The key ideas were

Process varying batch sizes based on how slow a path we are on.
Split the remote message queues by sizeclass
- This would allow us to quickly find messages containing the sizes we are using at the moment.
- When we are about to use the backend, process everything to see if we can consolidate existing memory to serve the request.

I am sure there is much more to discuss here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment