8 Commits
Author SHA1 Message Date
glitchminer 6fa532a436 Add benchmark results (Redmi A5 weekly refresh) 2026-08-23 06:28:07 +01:00
glitchminer dec2217726 benchmark: nightly Android perf 2026-08-19 (#21086)
Assisted-by: Claude Opus 4.8 (Anthropic)
2026-08-19 06:27:32 +01:00
glitchminer 7ae83936b2 charts: resource-lane account wording — fixture account, note the 2026-08-03 account change (#21248, #21753) 2026-08-17 08:53:23 +01:00
glitchminer b21896a53c benchmark: weekly Redmi A5 resources (power window) 2026-08-16 (#21753)
Assisted-by: Claude
2026-08-16 22:38:39 +01:00
glitchminer bf18404fd4 benchmark: weekly Redmi A5 resources 2026-08-16 (#21753)
Assisted-by: Claude
2026-08-16 22:27:26 +01:00
glitchminer 077e552b72 Add benchmark results (Redmi A5 weekly refresh) 2026-08-15 09:22:58 +01:00
glitchminer 46c52c0346 benchmark: nightly Android perf 2026-08-15 (#21086)
Assisted-by: Claude Opus 4.8 (Anthropic)
2026-08-15 06:48:13 +01:00
glitchminer 07ea877c28 charts: scope per device; add low-end (Redmi A5) view
run_environment.csv is keyed by (build, device) but the env lookup was keyed by
build alone — the Redmi rows overwrote the A36's and the gate scorecard lost its
2.38.2 baseline on every surface. Same hole in the per-surface charts: a surface
naming no device charted all devices (21 Redmi points on 8 A36 charts). Both now
scope to one phone; unnamed = the gate phone.

Adds a low-end scorecard, an A36-vs-Redmi comparison and per-surface Redmi trends
under docs/android/lowend/, published apart from the gate — the gate stays one
reference phone by design.

Gate verdicts are also withheld when only one side is below the measurement floor
(2.38.2 read Buy and Home at ~0.1s, so a normal 0.6s printed as "+0.5s slower").

Assisted-by: Claude Opus 5 (Anthropic)
2026-08-10 16:49:42 +01:00