Repository navigation
Document CPU cost of high HC compression levels - #141
Merged
Merged
Conversation
Fixes #121 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Fixes #121.
This adds a paragraph to the Javadoc of
LZ4Factory.highCompressor(int):2^(level-1)attempts, up to 65536 at level 17).The text doesn't claim that 12 is safe and 13 is not. Measured on 1 MiB of random bytes drawn from
{a,b}, level 9 took 0.9 s, level 12 took 5.5 s, and levels 13 to 17 took about 9.7 s, compared with about 35 ms on random data at any level. The doubling claim is limited to the Java implementations, because native lz4hc caps at level 12 and uses a different parser for levels 10 to 12.🤖 Generated with Claude Code