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

Message buffers allocation #1

Open
tcrain opened this issue Apr 21, 2020 · 0 comments
Open

Message buffers allocation #1

tcrain opened this issue Apr 21, 2020 · 0 comments
Labels
performance Performance improvement

Comments

@tcrain
Copy link
Owner

tcrain commented Apr 21, 2020

Allocation of buffers should be handled better.
Currently a message buffer may be copied multiple times after it is loaded from the network,
including when storing to disk.
After a message is read from the network there should be minimal copies.
It should also keep track of if a buffer is read only, so we know when it should be copied.
Also it would be nice to use a pool for message byte buffers to lessen impact of garbage collection.

@tcrain tcrain added the performance Performance improvement label Apr 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Performance improvement
Projects
None yet
Development

No branches or pull requests

1 participant