Refresh engine comparison tables after the second campaign round#2727
Merged
Conversation
Single-session re-measure of all lanes on main with sebastienros#2725/sebastienros#2726 merged. Extends the campaign notes with the round-2 wins (JSON scan fast paths, closure-read chain memoization) and records the measured-and-dropped direct-dispatch experiment: the builtin-call path is already at its cost floor, so the residual string-row gap is interpreter dispatch itself, not call ceremony. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
lahma
enabled auto-merge (squash)
July 21, 2026 18:06
This was referenced Jul 22, 2026
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.
Closes out campaign round 2 (#2725, #2726). Both tables re-measured in a single session on merged main; the "What changed" section now records the round-2 wins and — deliberately — the negative result: arity-specialized direct builtin dispatch was built, proven to engage on effectively all eligible calls, and measured flat, establishing that Jint's builtin-call path is already at its cost floor and the residual string-row gap vs V8 is interpreter dispatch itself. Documented so it isn't re-attempted.
Key rows this session:
dromaeo-string-base64-modern21.2 ms (25.9 at the campaigns' start),json-parse-modern17.6 ms with two-thirds of the campaign-start allocation,dromaeo-core-eval-modernlead over warmed V8 widened to 1.26×.🤖 Generated with Claude Code