Avoid heap allocation in Table #10
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
carlhoerberg
force-pushed
the
table-refactor
branch
from
c3dc815 to
c5f3622
Compare
carlhoerberg
force-pushed
the
table-refactor
branch
from
fdaafed to
e98b592
Compare
- Implement copy-on-write semantics to avoid unnecessary memory copies - Support read-only byte arrays (e.g. from mmap) with lazy copying - Optimize heap expansion to use minimal required memory - Reduce copying overhead when reading from bytes/IO streams
carlhoerberg
force-pushed
the
table-refactor
branch
from
48232c3 to
fd17166
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allocate memory manually for the Table instead of relying on
IO::Memory, which caused unnecessary heap allocations when the Table was empty.This PR produces between 7 and 20% higher throughput in LavinMQ.