npm run perf -- --browser times the same workloads in Chromium as a desktop
and as a phone (390x844 at 3x, CPU slowed 4x), one browser per version. Each
run collects garbage first and ends by forcing layout and the map canvas, so
deferred work counts. The jsdom DOM is about 30x slower than a browser's and
has no layout, so the interface rows need this.
Shared machines swing single runs by 30% on identical code, CPU time
included. A row now counts as slower or faster only when it moved 15% and a
Mann-Whitney U test gives p < 0.01 (15 runs a side by default). Identical
code: no flags in three full runs; a routing slowdown planted in a copy is
flagged in jsdom and on the phone.
The panel workload renders both selections every run instead of alternating,
which split its samples in two. CI drives the runner's Chrome through
playwright-core, no browser download.
scripts/perf-bench.js times routing, a game day, an action, panels, the
NOC dashboard and the map on tests/fixtures/big-network.json (104 POPs,
950 PNIs, 832 caches), base and head in alternating turns, and says
whether routing results changed. perf.yml runs it on every PR against
the base; perf-comment.yml posts the table as one updated comment.
New performance skill, CLAUDE.md rule, PR template and docs.
A network with a hundred POPs and a thousand peering ports froze the game for
most of a second every day and after every click, because routing checked all
~1,800 exits for each of ~14,000 flows. Now:
- compute(): exits are asked once per network which networks they reach, each
flow scans only those, and the first ECMP group is found without sorting. The
graph runs on city indices with a typed-array Dijkstra (same heap moves, same
ties), routers and per-link traffic are kept in typed arrays, the diverse-path
check reuses one live-link graph, and R.ef is put together when a link is read.
Results are bit-identical to before.
- Panels and the NOC dashboard are patched in place (morph) instead of being
rebuilt, so the browser no longer restyles 1,500 rows every tick. Buttons whose
action changed are swapped out, keeping #44's tap protection.
- The Networks tab works out each IX port's sessions once instead of once per
network.
- draw() reuses screen-point buffers, a per-frame pair index and cached label
widths, strokes the dotted fiber line on the path it already has, and uses
native roundRect: about a third fewer canvas calls per frame, same output.
Adds site/i18n/pt.js with all 2429 strings, registers Português in the
language list (picked automatically for pt-* browsers), caches it in the
service worker, and runs the full screen tour in Portuguese in the tests.
Levels now run to 13, driven by a requirements table (peak, POPs,
continents). Each unlocks something: seven router models up to 3.2T with
3.2T ports and 12.8T waves, C+L line systems, 3.2T transponders, eight
pairs per land trench, a 102.4T fabric, 100T scrubbing, six customer
types, and free PNIs from paid-peering networks. Four traffic eras raise
the eyeball ceiling so the higher levels are reachable on a 47 Tbps map.
Default router upgrades follow the badge-less main line per class; port
and wave tiers past 1.6T/6.4T only show once unlocked. Old saves keep
their level; land trenches clamp to four pairs below level 12.