Fix json_pipeline_small parse threshold#704
Merged
proggeramlug merged 5 commits intoMay 12, 2026
Merged
Conversation
11cb8e2 to
6130337
Compare
6130337 to
2920ae9
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.
Summary
Fixes #437 by raising the lazy JSON parse auto-mode lower bound from 1 KB to 64 KB. The 21 KB
json_pipeline_smallfixture now stays on the direct parser, avoiding lazy-header and forced-materialization overhead on an iterate-all workload.This also updates the lazy JSON predicate regression fixture so it still exceeds the auto-mode threshold and refreshes the related docs.
Impact
json_pipeline_smallnow runs through the faster direct parser in auto mode.PERRY_JSON_TAPE=1.Measured Improvement
On the local 20-run issue reproduction:
7fc66fa8andoutput_match=truefor all measured runs.Conflict Resolution
Rebased onto the latest
main(0.5.867) and resolved the conflict inCargo.lockby keeping the current base lockfile. The PR now only changes the runtime threshold, lazy JSON test fixture, and related docs.Validation
cargo check --release -p perry-runtime --lockedtest-files/test_json_lazy_predicates.tswith Perryjson_pipeline_smallPerry workload and ran 20 measured iterations with the honest_bench output checker