WIP Experiment with different kind of allocator for backend.#824
Draft
WIP Experiment with different kind of allocator for backend.#824
Conversation
Add a backend range that delays returning memory to the next level. This reduces the pressure on the backend global allocator.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The buddy allocator for large objects and chunks leads to good fragmentation behaviour, but can result in a lot of internal fragmentation as the blocks it returns can be twice the size requested. This PR makes the blocks have more sizeclasses using a DougLea/TLSF like consolidation strategy, but with some modification to handle the alignment requires for snmalloc.