Reuse fixed token prices in level 9 parsing - #35
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.
Level 9 repeatedly recalculates the same fixed token prices while comparing match lengths. Cache length prices and hoist distance pricing out of that loop, preserving candidate order and ties.
Linux development JMH measured 1.11x on Rainier and 1.06x on the map-tile fixture, with Sunrise unchanged. These are short runs, with raw samples and errors in
performance/2026-09-09-costspeed/RESULTS.md. Saved Kompress measurements are reused unchanged.Linux JVM tests passed; all 70 corpus/level outputs passed both JDK and KFlate decoding and matched baseline SHA-256 hashes. All seven level 9 compression cases completed. Independent change against
dev-1.1.0.