Comment by altcognito
14 hours ago
14x is a lot commits, but I seriously have doubts that some pushes are putting them over the edge. (as many have suggested)
> GitHub Actions
For me this is probably this biggest culprit along with the general pressure of AI against the hardware. Github actions became really popular. So many of those 14x commits are generating real CPU and network load.
This is a really non trivial problem. They can't just wall it off. They have real customers on that stuff.
Why do you think that?
GitHub Actions is 'simpler' to scale, it's just a bunch of runners, and Azure has a lot of capacity for VMs (mostly). Git itself is a compute intensive process and is far more interlinked.
Not sure how you see git repos as a compute intensive process. A single git commit takes milliseconds. It's mostly a hash calculation and a small file transaction. They've added some database stuff around the edges, but that is pretty tame as well.
Actions are unbounded, take minutes to resolve - sometimes hours and there are megabytes, gigabytes of network transactions.
Scaling commits is a load balancer and some more instances of a thing you’ve built over and over.
Scaling actions is VMs, networking, imbalances in load, memory, insuring that folks aren’t running VM training against your infrastructure. Oh, and maybe you want to make sure folks aren’t trying to hack that infrastructure as well.
It is a very, very hard problem.
I'm sure GitHub Actions are more intensive, but that doesn't make it harder to scale, which is what martinald said.
> Scaling actions is VMs, networking, imbalances in load, memory, insuring that folks aren’t running VM training against your infrastructure.
That infra scaling is what the cloud provider can easily offer.
Meanwhile, GitHub repos/issues/PRs is all the business logic that they've written, evolved over time.
Many coupled distributed DBs, indexes, consistency concerns, etc.
That's trickier to scale.