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

Allocation mechanisms improvements #69

Open
1 of 3 tasks
m4drat opened this issue Sep 1, 2022 · 0 comments
Open
1 of 3 tasks

Allocation mechanisms improvements #69

m4drat opened this issue Sep 1, 2022 · 0 comments
Assignees
Labels

Comments

@m4drat
Copy link
Owner

m4drat commented Sep 1, 2022

  • ❓ Change allocation logic (firstly reuse all available space in free list, and only then allocate new arena). This one is under a question mark, because with that implementation we are losing benefits of simple bump allocator. But the idea in general is that we should use free-list more.
  • ✔ Try to reuse the most appropriate chunks from chunk treap first (GetFirstGreaterOrEqualToChunk -> upper_bound). To do so it is a great idea to implement iterator for ChunkTreap #39 (just to use std::lower_bound)
  • ✔ Before doing anything, complete Performance comparisons (mimalloc, malloc, jemalloc) + cpu/memory Profiling #29 and collect some base measurements.
@m4drat m4drat added this to the Memory Manager milestone Sep 1, 2022
@m4drat m4drat self-assigned this Sep 1, 2022
@m4drat m4drat added the Medium label Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant