NodeFlair - Tech Salaries, Jobs & more’s Post

We made our CI 2.86x faster, 83% cheaper 🚀 Here's how: But firstly, why is a fast build for CI crucial? Because it keeps your momentum alive by providing quicker feedback, preventing the soul-sucking downtime that kills productivity. 🐌 And here's why our CI build at NodeFlair - Tech Salaries, Jobs & more were taking so long: 1) GitHub Action is slow - initializing container alone takes 1 minute. 2) Tests run slow - we were running them one after another. Apparently if you are unlucky, GitHub will run your workflow with old hardware from 2015. In comparison, me running it locally on my M2 MacBook Air is ~3x faster. 🚀 So here's how we solved it: 1) Running tests in parallel - our runners have 2vCPU so they can run the tests concurrently - cutting time taken to run tests by 16%. (FYI fellow Rails folks, we are using Flatware) 2) Switching to BuildJet runners. By changing 1 line of code, overall build time drops by 33% - it's 50% cheaper too! 3) Also switching to BuildJet cache - 20GB instead of GitHub's 10GB. With a larger cache, there's a higher probability that previously cached dependencies will still be available for subsequent builds, reducing the need to fetch them again. And here’s the kicker: BuildJet is not only 50% cheaper per minute, but with its blazing-fast runners, we’re slashing our CI costs by up to 83%. This isn’t some paid shill — I’m telling you to give it a go yourself. See the difference firsthand. Once again, the art of doing more with less fuels my passion. It’s how we scale swiftly and stay lean. 💡 UPDATE: We switched to Blacksmith because it's even faster and cheaper - 3x faster, 6x cheaper! https://lnkd.in/gyJYkupk