Reduce TAR entry buffer allocations - #40
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
TAR entry reads repeatedly grow their buffers even when the entry size is available. Preallocate for entries between 513 bytes and 64 KiB, bounded by the remaining decompression budget, while preserving read errors and size limits.
The existing
BenchmarkOpenBytesTarGzfixture uses about 49% fewer allocated bytes and 44% fewer allocations. Add browsing benchmarks across entry sizes and regression coverage for extraction, prefixes, duplicate paths, truncated payloads, checksum errors, and decompression limits, plus a payload round-trip fuzz test.