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.

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

Realm: Improve fragmentation caused by basic range allocator #1766

Open
apryakhin opened this issue Sep 25, 2024 · 0 comments
Open

Realm: Improve fragmentation caused by basic range allocator #1766

apryakhin opened this issue Sep 25, 2024 · 0 comments
Labels
enhancement Realm Issues pertaining to Realm
Milestone

Comments

@apryakhin
Copy link
Contributor

That shouldn't be a duplicate issue as far as I can tell. @lightsighter proposed and implemented a replacement for realm's basic range allocator:

The basic range allocator maintains a single unsorted list of free blocks. The incoming allocation always grabs the first entry from the free list that is big enough for the requested size and returns the remaining part as a new free block. Although this strategy is simple, it can result in memory fragmentation.

As part of this GitHub issue, we need to run some tests, add benchmarks on the "Size-Based Range Allocator" possibly work on replacing the existing one. Ideally, we should find a real-world existing application that this would help improve.

@apryakhin apryakhin added this to the realm-24.11 milestone Sep 25, 2024
@apryakhin apryakhin added the Realm Issues pertaining to Realm label Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Realm Issues pertaining to Realm
Projects
None yet
Development

No branches or pull requests

1 participant