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

Reduce memory usage #5

Open
ibraheemdev opened this issue Mar 29, 2022 · 3 comments
Open

Reduce memory usage #5

ibraheemdev opened this issue Mar 29, 2022 · 3 comments

Comments

@ibraheemdev
Copy link
Owner

See jonhoo/flurry#80 (comment).

@ibraheemdev
Copy link
Owner Author

#19 should address the issue. We still require an extra two words of memory per object, but getting rid of those is more difficult. We would have to make links optional but verify that they are used when epoch tracking is enabled. That would allow moving the reservation list pointers into the batch allocation for each node, reducing the metadata to one word per object.

@ibraheemdev
Copy link
Owner Author

#24 further reduces the overhead to one word. The final improvement that could be made is making epoch tracking manual by making Link/Epoch an argument to retire and moving reservation lists into the batch allocation, allowing nodes to be entirely optional.

@ibraheemdev
Copy link
Owner Author

When batch sizes are large we can also try to estimate the number of entries that will be used in reservation lists and keep them separately, avoiding extra memory usage for the rest of the batch.

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