EKMISSION · HOURLY REFRESH

Where the 89 seconds go

One real run, 2026-08-20. Thirteen steps, but nine of them finish in under two seconds — so adjacent fast steps are merged into one row and named. The deploy alone is 44% of the run.

Duration of each stage in the hourly ekmission refresh Gantt chart of one 89-second refresh run: the deploy takes 39 seconds and the screenshot step 24, together three quarters of the run, while nine generators finish in under two seconds combined. 0s 10 20 30 40 50 60 70 80 89 Gate, meter, ccusage 2s Wallet 5s Fleet, projects 11s · GitHub API Shots 24s · 7 sites screenshotted Usage, estate, attention 8s Deploy 39s · only fires when the content hash changed LAST 18 RUNS ONE BOX PER RUN — NOT THE TIME AXIS 1 FAILURE IN 18 LEGEND BAR LENGTH = SECONDS · 8PX PER SECOND VIOLET = THE STEP THAT DOMINATES SOURCE: LEDGER

The run as a list

Gate, meter, ccusage
2s
Wallet
5s
Fleet, projects
11s
Shots · 7 sites
24s
Usage, estate, attention
8s
Deploy
39s · 44%
Total
89s
Last 18 runs
1 failure