"How We Made the Rust CI 75% Cheaper"
summary
Rust CI cost falls to about 25% of its previous bill by replacing oversized paid runners with free standard runners, splitting test-heavy jobs, freeing disk space, and shifting some workloads to AWS CodeBuild and sponsor credits. The auto-build runs 84 jobs totaling ~150 CPU hours per attempt and currently takes ~3 hours; org-wide CI uses ~3 million minutes/month (~6 years CPU). Key outcomes: from 33 large runners to 4, cost per merge attempt $141 → $34, monthly spend ~$47k before optimizations.
AI-written summary · about
chapters (11)
- 0:00Introduction to Rust CI
- 5:17Constraints and costs of CI
- 8:51Optimization strategies begin
- 9:40Overprovisioned jobs conversion
- 11:41Cache and runner challenges
- 13:15Freeing up disk space
- 14:44Splitting jobs for efficiency
- 17:31ARM runners and final moves
- 18:16Results and cost reduction
- 19:18AWS CodeBuild integration
- 20:35Future of Rust CI
related talks
26mFaster, Cheaper, Leaner: Horizontally Scaling a CI Pipeline
24mUnlocking CI Performance in the Age of Agentic Development
10m{ Fast, Cost-effective } – Choose Two
20mMaximize development efficiency with expert CI/CD strategies
24mSupercharging CI: Test Suite Optimization for Speed, Stability, and Savings
58mDitch Your Expensive CI/CD and Bui
25m100 Million Lines of Code, Millions of $ Saved, 0 Wasted Builds; AI Powered CI @ Atlassian Scale
30mThe Bitter and the Sweet of Running a Planet-Scale Build &...