Fix inflate_fast_help loop bound
#260
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
Codecov ReportAttention: Patch coverage is
|
ad248e5 to
8ed2c63
Compare
bjorn3
reviewed
Dec 10, 2024
|
|
||
| #[inline(always)] | ||
| pub fn bytes_remaining_including_buffer(&self) -> usize { | ||
| (self.end as usize - self.ptr as usize) + (self.bits_used as usize >> 3) |
Collaborator
There was a problem hiding this comment.
Using / 8 instead of >> 3 may be a bit clearer and will optimize to the same assembly.
Member
Author
There was a problem hiding this comment.
we can make a pass over the repo at some point. I think zlib-ng never updated this, and the original zlib that it forked was written at a time when apparently that optimization was not (effectively) guaranteed.
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.
When you finally spot the thing... 🤦 we are now faster than zlib-ng for all chunk sizes.
It's only a marginal improvement for chunk size 2**4, but quite significant for what are probably the most common chunk sizes (very small chunk sizes likely indicate io-bound operation).
After fixing the bug of exiting the loop too early (first commit), I then made the bound a bit more accurate, and finally refactored the output type of
len_and_friends. The final commit has no performance impact.