Why is CI so Damn Slow?
summary
CI is slow because tools pay two costs installation and runtime and many JS tools incur both by pulling node and hundreds of deps before running each job Rome replaces npm installs with native Rust binaries and collapses redundant parsing work into one pass using a concrete syntax tree this yields concrete numbers eslint prettier rules take ~5–6s webpack similar while prettier hits >2s on big files Rome formats that file in 335ms and dojo in 10ms versus 75ms prettier 2s vs rome 335ms the linting goal is a 10x speed target for linting
AI-written summary · about
chapters (6)
related talks
36mPerfecting CI pipeline for Ember projects. Faster and with more insights.
24mUnlocking CI Performance in the Age of Agentic Development
25m"How We Made the Rust CI 75% Cheaper"
24mSupercharging CI: Test Suite Optimization for Speed, Stability, and Savings
05mTips for Speeding Up Cargo Build in CI
20mSpeed up your CI & Save the Environment
20m20 Nuggets in 20 Minutes - Get more from your CI
20mDevelopment efficiency with expert CI/CD strategies