‹ BackHN Continuity

Thread

AI coding has made CI a bottleneck, so we reworked ours to keep up

317 points · 408 comments · julian_digital

  1. classictraffic · · focus · HN ↗
    > Moving our workloads off GitHub Actions to third-party runners with faster CPUs, higher-performance storage, and better cache infrastructure gave us faster machines to run the same pipeline on

    Yeah, was not surprised to read this. Actions is convenient if you already use GitHub, but it can also be pretty slow. Given reliability is also a major issue with GitHub these days I expect to see more orgs moving to different pipelines

    1. speedgoose · · focus · HN ↗
      I wonder how much faster GitHub actions could be if they weren’t running on Azure. Because Azure is either slow or very expensive.
      1. stackskipton · · focus · HN ↗
        It's not Azure as much as self-hosted runners are basement bin servers on clearly massively oversubscribed machines.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.