custom gzip stream implementation - #95
Draft
austin-weeks wants to merge 5 commits into
Draft
Conversation
austin-weeks
force-pushed
the
gzip-optimization
branch
from
August 13, 2026 06:31
656c14b to
287f8dd
Compare
Owner
Author
|
This requires trifectatechfoundation/zlib-rs#556 to be accepted and merged Update: PR has been merged! Now waiting on the change to be released, as crates.io will not allow me to release this change with a patched dependency. |
austin-weeks
force-pushed
the
gzip-optimization
branch
from
August 15, 2026 00:11
5a59585 to
d681820
Compare
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
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.
This ditches the
async_compressionrate for a custom implementation usingzlib-rs.Benchmarks
At 500 sustained concurrent requests:
The existing implementation peaks at
362Mmemory usage.This branch's implementation (with level 9, window bits 11, and memory level 3), peaks at
164Mmemory usage.The resulting compression ratio is only slight worse (less than
10%), while memory is reduced by55%!