Refresh engine comparison benchmark results#2612
Merged
lahma merged 1 commit intoJul 9, 2026
Merged
Conversation
Full re-run after the 2026-07 interpreter-parity campaign (sebastienros#2600-sebastienros#2606, sebastienros#2608-sebastienros#2611). Highlights vs the 2026-07-07 refresh: dromaeo-core-eval -40% (1.52 -> 0.92 ms, taking first place from NiL.JS), dromaeo-3d-cube -19% time / -35% allocation (7.38 -> 5.99 ms, moving ahead of NiL.JS - only the IL-compiling engine remains faster), stopwatch -7% (tied with the best interpreter, ahead of Jurassic), stopwatch-modern -13% (tied with Jurassic), object-array -10%, object-regexp -13%, object-string -5%. Competitor versions unchanged; their rows served as thermal canaries (all within a few percent of the previous refresh). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
lahma
enabled auto-merge (squash)
July 9, 2026 19:23
This was referenced Jul 13, 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.
Full EngineComparison re-run on current main after the 2026-07 interpreter-parity campaign (#2600–#2606, #2608–#2611), replacing the 2026-07-07 table.
Headlines vs the previous refresh
Competitor versions unchanged (Jurassic 3.2.9, NiL.JS 2.6.1722, YantraJS 1.2.406); their rows served as thermal canaries and sit within a few percent of the previous refresh (e.g. NiL.JS core-eval +0.2%, YantraJS cube ±0%), so the window is comparable.
Prose sections ("At a glance", "Where Jint leads/trails", "What's new") updated to match; the "trails" section now contains only the structural interpreter-vs-IL-compiler gap.
🤖 Generated with Claude Code