feat(site): lead the benchmarks page with a scoreboard and drawn ratios - #727
Open
Exoridus wants to merge 5 commits into
Open
feat(site): lead the benchmarks page with a scoreboard and drawn ratios#727Exoridus wants to merge 5 commits into
Exoridus wants to merge 5 commits into
Conversation
The page opened with a paragraph of generated prose and then repeated every comparison as a wide table whose mechanism column wrapped over several lines, so the numbers were the hardest thing on it to find. It ran to about 10500 px at 1440 px wide, and the practices it is published under sat above the results. Rearrange it around the figures. A scoreboard leads with one line per arm - a rendering backend against one opponent, or one physics arm - showing how that pair's comparisons came out as a strip and as counts; nothing is summed across lines, because the arms answer different questions. Under it, one table per domain whose columns are the pairs and whose rows are archetypes, so a single archetype reads across both backends and every opponent on one line. The ratio is drawn as a bar on a log axis with the published factor beside it, and the medians, the p95 of the same window and the range the pooled runs observed sit under it on lines that never wrap. Methodology, reproduction and fairness move below the tables. A comparison whose runs disagreed no longer prints a verdict placeholder and a sentence about what each run concluded. It keeps its numbers and shows the ratio band those runs spanned, drawn without a side - the one figure the page derives rather than reads, from the published extremes of both arms, so a cell the measurement could not settle still says what was measured. The docs shell caps its width for prose, which a table page has no use for, so DocsLayout gains a wide variant. The benchmark hues become their own tokens: the shared semantic palette is tuned for the dark surface and washes out under a 6 px bar on the light one. Claude-Session: https://claude.ai/code/session_01Y3YY9obdzhWK7nBPby2jK5
Exoridus
enabled auto-merge (squash)
September 9, 2026 01:29
Bundle ReportChanges will increase total bundle size by 137 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: site-server-esmAssets Changed:
|
Exoridus
disabled auto-merge
September 9, 2026 01:35
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.
The page opened with a paragraph of generated prose and then repeated every
comparison as a wide table whose mechanism column wrapped over several lines,
so the numbers were the hardest thing on it to find. It ran to about 10500 px
at 1440 px wide, and the practices it is published under sat above the results.
What changed
opponent, or one physics arm, with that pair's outcomes as a strip and as
counts. The split is per arm and never per backend - a backend line pooled two
different opponents into one strip and showed a mix that belonged to neither.
Nothing is summed across lines and no line is ranked against another.
single archetype reads across both backends and every opponent on one line.
ExoJS gets a column of its own per backend instead of being repeated inside
every cell.
it. The axis is scaled to the widest ratio in that table, up to two decades;
a bar past that is drawn cut and keeps its exact factor.
the range the pooled runs observed sit under every bar, on lines that never
wrap.
structural evidence, the omitted rows, the WebGL1 arms and the caveats become
collapsed asides under them.
A comparison whose runs disagreed no longer prints a verdict placeholder and a
sentence about what each run concluded. It keeps its numbers and shows the ratio
band those runs spanned, drawn without a side. That band is the one figure the
page derives rather than reads, computed from the published extremes of both
arms, so a cell the measurement could not settle still says what was measured.
It is never a verdict: it has no side, and a band straddling 1.00 is the
statement that the runs could not separate the pair.
Unchanged: every number and verdict still comes from the signed profile, nothing
is aggregated into a score or an overall winner, losses are published like wins,
rows the harness left out are listed with their reasons, and the page still
renders with no profile at all. The harness and the profile JSONs are untouched.
Layout
DocsLayoutgains awidevariant: the docs shell caps itself at 1260 px forprose, which a table page has no use for. The benchmark hues become their own
tokens - the shared semantic palette is tuned for the dark surface and washes
out under a 6 px bar on the light one.
BenchMeasurement.astrois gone; the cell composes both arms now.Validation
site/pnpm check-ts,pnpm gates typecheck,pnpm gates lint,pnpm gates sync,pnpm gates site,git diff --check, and the browser lane the pre-pushhook selected (
site:build+ example smoke, 24 passed). Checked in the devserver at 1600 px and 760 px in both themes: no body overflow, no truncated
cell, page height about 3870 px.
https://claude.ai/code/session_01Y3YY9obdzhWK7nBPby2jK5