bench: re-measure the macOS reference profile on the published plan - #747
Merged
Merged
Conversation
Exoridus
enabled auto-merge (squash)
September 15, 2026 02:04
Bundle ReportChanges will decrease total bundle size by 202.93kB (-0.39%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: site-server-esmAssets Changed:
|
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.
What
Re-measures the macOS profile (
m3-max-macos-27-beta-webkit.json) onnextafter #745, from three separate WebKit runs pooled withbench:compare --profile.verify:bench-resultsis green.Why it shrinks
The profile drops from 253 rendering cells to 108, and the
overdrawarchetype disappears. That is the point of the change rather than a loss.#733 published this machine on the full ladder.
fullis the development matrix — it exists so no historical cell stops being reachable — and it carries the ExoJS-internal probes (overdraw,split-screen, the material and mesh rows,instanced-batch) that the published catalog leaves out on purpose: a competitor arm renders some other scene on those, so they are development rows and never a published comparison. Publishing them states a comparison the harness itself does not claim.referenceis the published plan, and the site filters nothing — it carries display labels for those probe archetypes and shows whatever a profile contains. So this run puts macOS back on the same plan Windows uses: 108 cells against 107, first time both machines answer the same matrix.Follow-up worth having
Nothing stops a
fullprofile from being committed again. Either the benchmarks page should refuse archetypes outside the published catalog, orverify:bench-resultsshould reject a profile that contains them. Not in this PR.https://claude.ai/code/session_013jqQeGU6gwsQhYDFrKiN1A