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

statically allocated bitmaps #268

Open
bgoglin opened this issue Oct 12, 2017 · 2 comments
Open

statically allocated bitmaps #268

bgoglin opened this issue Oct 12, 2017 · 2 comments
Milestone

Comments

@bgoglin
Copy link
Contributor

bgoglin commented Oct 12, 2017

@elfarouk wants statically-allocated bitmaps to avoid memory fragmentation. Not easy with the current implementation. If we implement bitmaps that are already preallocated #255 and we say that applications using higher bits are buggy, we could extend to statically allocated bitmaps.

@bgoglin bgoglin added this to the v2.1 milestone Oct 12, 2017
@sthibaul
Copy link
Contributor

AIUI it's just a performance question. We could let the application just configure the default bitmap size, and use that as default allocation for bitmaps. If the application doesn't go beyond it, there won't be reallocations, if it does, there will be reallocations, but that will only have performance consequences.

@bgoglin bgoglin modified the milestones: v2.1, Future Sep 26, 2019
@bgoglin
Copy link
Contributor Author

bgoglin commented Sep 26, 2019

Moving this to Future instead of v2.1 since @elfarouk didn't provide a test case for looking at fragmentation issues.

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

No branches or pull requests

2 participants