bench: refresh json-polyglot and polyglot results (quiet host, 2026-08-06) - #7476
Merged
Conversation
…8-06) First measurement since #7473 fixed the JSON.stringify crash that made perry produce no row at all for json_polyglot/field_access. Measured on a verified-quiet host: CPU active confirmed <=25% for 60 consecutive seconds before each leg (15.2%, 15.1%, 3.7%, 4.5%), AC power, pinned Node v22.23.1 and Bun 1.3.14, 11 runs per cell. Headline: perry now WINS the JSON roundtrip against both runtimes -- 194 ms vs bun 221 vs node 384. field_access is the opposite: 2981 ms against bun's 223, and the mark-sweep/no-lazy variant beats the default by 2.2x (1340 vs 2981) on a quarter of the memory (58 vs 218 MB). The lazy tape is a large net loss on that access pattern, which is a well-isolated optimisation target.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughUpdated two benchmark result documents with August 6, 2026 metadata and newer measurements for runtime performance, memory usage, variability, and result ordering. ChangesBenchmark results
Estimated code review effort: 1 (Trivial) | ~5 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
First measurement since #7473 fixed the
JSON.stringifycrash that made perry produce no row at all forjson_polyglot/field_access.Conditions
Verified-quiet host — CPU active confirmed ≤25% for 60 consecutive seconds before each leg (15.2%, 15.1%, 3.7%, 4.5%), AC power, pinned Node v22.23.1 and Bun 1.3.14, 11 runs per cell, median + p95 + σ.
Headline: perry wins the JSON roundtrip
Faster than both, with tight variance (σ 1.5).
field_access is the inverse, and the variant split is the finding
The lazy tape is a 2.2× net loss on this access pattern, on ~4× the memory. That is a well-isolated optimisation target rather than a diffuse gap — the same tape that wins roundtrip loses field_access, so the decision could be per-workload.
Scope
Results files only; no code. The public artifact itself still cannot be published — #7475 (
object_deep_clone/promise_all_chainsfail under the auto-optimize path) is the remaining gate, and it is pre-existing rather than anything from this run.Summary by CodeRabbit