Build speed: v0.27.8 against the perf/build-speed branch

The xtask bench-gen app (Model fields = update arms = N, 8 modules, seed 1) built with sky build --target web:app, by scripts/bench-build.sh --cases app --sizes "50 100 200" --targets web:app --reps 1.

Scenarios: first is a fresh directory with the normal Sky Go cache; warm the same directory again; newdir the same sources in a new directory; edit one string literal changed in one view module (in the new directory); cold a fresh directory with an empty temporary GOCACHE. Wall and CPU in seconds (CPU is user + sys of sky and all its children), peak RSS of the largest single process in MB.

Nscenariowall beforewall afterCPU beforeCPU afterpeak RSS beforepeak RSS after
50first40.1239.7880.21164.37692894
50warm3.131.683.853.56144127
50newdir33.843.4056.586.26646612
50edit29.5623.4738.3239.15602595
50cold52.8730.16161.81137.17782837
100first51.6427.8779.2746.56997619
100warm10.962.4711.564.62278183
100newdir49.984.2079.007.38991601
100edit45.3227.2860.8846.17984619
100cold70.2231.49181.33140.46955846
200first131.4836.66183.8563.572705860
200warm65.224.5565.247.54880437
200newdir157.085.51278.659.042915612
200edit125.5937.46163.9163.652710875
200cold168.1833.44273.82155.892764902

Reading it:

docs/perf/build-budget.json holds the budget the build-perf CI job compares against; see its note.

The budget run (ci-shape.json)

scripts/bench-build.sh --reps 3 --cases "app skyshop" --write-budget docs/perf/build-budget.json on the same Mac, branch compiler: the shape the build-perf CI job runs (generated app at N=50 and N=100 for web:app and web, and examples/13-skyshop). Its medians (the prime scenario excluded) are the darwin-arm64 entry of docs/perf/build-budget.json. Each rep's edit carries a per-run token, so it is a real edit-rebuild every time (web:app: 23.8 to 27.5 s, most of it brotli of the new wasm).