🛠CI Bottlenecks Cut by 50%: Faster PRs and Runner Times
CI now 34% faster, PR wait time down to 5 minutes
TL;DR
A team optimized CI to reduce bottlenecks, cutting PR wait time to 5 minutes and runner time in half. Key improvements include offloading to third-party runners and optimizing TypeScript builds.
The team tackled CI bottlenecks by optimizing jobs and infrastructure, reducing PR wait time from over 6 minutes to just over 5 and cutting runner time per test in half. They moved workloads off GitHub Actions to third-party runners with faster CPUs, achieving a 34% speed boost. Upgrading to tsgo, the native TypeScript compiler, slashed weekly median tsc check time by 73%. These optimizations are crucial for teams with large TypeScript codebases and high CI costs.
Key Points
PR wait time reduced from over 6 minutes to just over 5 minutes.
Runner time per test cut roughly in half, improving CI efficiency.
Moving workloads to third-party runners with faster CPUs boosted speed by 34%.
Upgrading to tsgo, the native TypeScript compiler, slashed tsc check time by 73%.
Optimizing change-detection jobs reduced median duration from 26 to 8 seconds.
Why It Matters
If you're working on a TypeScript project with high CI costs, these optimizations can significantly reduce PR wait times and runner costs. Teams using GitHub Actions can see a 34% speed boost by offloading to third-party runners. The tsgo compiler alone cuts tsc check time by 73%, making CI more efficient for large codebases.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,484 builders reading daily.