A medium production web:app, before and after

The build-speed work started from one real application: a medium production Sky.Spa app built with --target web:app. It is a private project, so its name, its modules, its types and its fields are withheld here. Only totals and per-stage timings are given.

Field data before the work (v0.27.8 line)

These are the user's own timings of a full --target web:app build, reported when the work started (.claude/AUTONOMOUS_GOAL.md). They are wall-clock observations, not runs of a script in this repository.

MachineBuild time
Spot VM, 8 CPUs, 32 GB29 min
the user's Macabout 25 min
GitHub-hosted runner30 to 38 min

On this branch

The user ran SKY_TIMINGS=1 sky build --target web:app on the 16 GB Apple silicon Mac (8 CPUs) used for the build-speed work, go1.26.1, with the compiler built from two commits of perf/build-speed. The figures are the totals from the SKY_TIMINGS report.

Commit 58fec7490 (an intermediate commit)

StageTime
total142.5 s
lowering, parent process49.4 s
backend leg44.9 s
frontend leg13.0 s
brotli27.6 s
peak memory3.5 GB

Commit 5d30f9127 (after the call-site harvest fix)

StageTime
total21.8 s
type check, parent process1.99 s
lowering, parent process1.80 s
split3.33 s
frontend leg5.79 s
backend leg8.15 s
peak memory1.25 GB

In this run go build and brotli were cache hits: the app's source had not changed since the previous build, so the Go packages and the .br / .gz files came from the caches. The 21.8 s is therefore a rebuild of unchanged source, not a cold build. A cold build of the same commit, and a build on the VM or the runner from the field data above, were not measured.

Reading it