The bit about the test suite running twice is the whole post. We found the same thing last year and it was a stray watch flag in a config nobody had opened since 2022.
How we cut our build from 40 minutes to 6
Published Engineering Priya Raman · · 9 min read
Performance
The seven days since it went out
Views
41,200
Against 8,900 for the median post
Median read
4m 12s
Of an estimated nine-minute read
Newsletter sign-ups
318
0.8% of everyone who arrived
- Most traffic from
- Hacker News — 22,400 arrivals
- Then
- The newsletter — 7,100 · search — 4,800
- Read on a phone
- 61% of sessions
Comments
—
Speed up your CI with our tool, free trial at fastbuilds dot example, first month half price.
Would you publish the actual timings per stage? Six minutes is a headline; the shape of where the other thirty-four went is the useful part.
Nothing left to moderate
Approved comments appear under the post straight away.
History
Eleven days from first draft to live
-
Published
Went out on the 09:00 slot, as scheduled.
-
Scheduled for 25 August
Held for the Tuesday slot rather than going out beside the release note.
-
Review approved
Second pass. The benchmark table was rebuilt from the raw runs.
-
Changes requested
Two numbers in the table disagreed with the ones in the prose.
-
Sent for review
2,300 words, cover chosen, slug set to /blog/faster-builds.
-
Draft created
From the retrospective note on the build working group.
Details
- Status
- Published
- Address
- example.com/blog/faster-builds
- Category
- Engineering
- Author
- Priya Raman
- Published
- Last edited
- Length
- 2,300 words · 9 min read
Cover
Shown at 16:9 in the feed and cropped square in the newsletter. Replace it in the editor.
What search sees
example.com › blog › faster-builds
How we cut our build from 40 minutes to 6
Six weeks of profiling, one cache that was never warm, and a test suite that had been running twice.