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

Switching to a proper memory-pool implementation #99

Closed
kabicm opened this issue Oct 4, 2021 · 1 comment
Closed

Switching to a proper memory-pool implementation #99

kabicm opened this issue Oct 4, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@kabicm
Copy link
Collaborator

kabicm commented Oct 4, 2021

The current implementation allocates one large piece of memory from which all the buffers are taken. This has its advantages, but adds the requirement that all the required memory must be available as one, consecutive piece, which might not be possible in case of fragmentation (see here).

We want to switch to using a proper memory pool.

@kabicm kabicm added the enhancement New feature or request label Oct 4, 2021
@kabicm
Copy link
Collaborator Author

kabicm commented Jun 29, 2022

This is a reasonable improvements, but doesn't seem to affect the production runs, so we will close it now. We might reopenn it at some later point.

@kabicm kabicm closed this as completed Jun 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant