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.
Hello, here at @alpineiq we use msgpack extensively, however as some of our caches grew, we hit some roadblocks with memory for decoding.
I took a crack at the decoder and come up with this PR:
bytesAllocLimit/sliceAllocLimit/maxMapSize
, always allocate the full size since it's known beforehand.I know it might look like a micro-optimization but it's extremely significant at the scale we use it for, it's the difference between running OO< on a 5.75TB instance and only using 1.4TB.
Our internal benchmark (Can't provide a test file, but it's about 159mb, the real files are 1-2gb):
Benchstat of the all msgpack tests, no real changes: