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

Consider adding worst-case fragmentation bound to README #95

Open
ntysdd opened this issue Aug 4, 2022 · 0 comments
Open

Consider adding worst-case fragmentation bound to README #95

ntysdd opened this issue Aug 4, 2022 · 0 comments

Comments

@ntysdd
Copy link

ntysdd commented Aug 4, 2022

Currently there's no worst-case fragmentation analysis in README.

Considering this is what distinguishes Mesh most from othere allocators, I think it's important to give a worst-case bound for fragmentation. Or maybe 99.9 percentile if absolute worst-case can't be guaranteed.

A comparison to other popular allocators may be helpful too.

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

No branches or pull requests

1 participant