Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft turns to AWS as GitHub faces AI capacity crunch

runtimewire.com

Post reply on HN
Print view View original

11–20 of 83 posts

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#11

Post by 3eb7988a1663 »

BobbyTables2 wrote: post #9
csbrooks wrote: post #2

> commits were on pace to hit 14 billion in 2026, up from 1 billion in 2025 So AI means 14x the checkins? That's not 14x features completed, but still... wow.

Is that even a lot? Spread over a year, roughly estimating a generous 4 kbytes of data per commit, comes out to a throughput of a little under 2 MB/s. Of course, it isn’t spread out uniformly and there is also a lot of hashing and other things going on. Maybe pulls and clones drive more I/O ?

I suspect there is a cacophony of work that happens when a commit hits the server. That request needs to get replicated, git repositories need to be repacked, pull requests need to calculate diffs, CI jobs need to execute, on and on.

That's also just assuming the good-faith usage. There are probably plenty of adversarial and poorly behaved scrapers that are putting additional load on the system.

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#14

Post by shimman »

N_Lens wrote: post #8
csbrooks wrote: post #2

> commits were on pace to hit 14 billion in 2026, up from 1 billion in 2025 So AI means 14x the checkins? That's not 14x features completed, but still... wow.

AI has 100x'd our productive capacity such that we're moving at unforeseen speeds at digging holes and refilling them!

This is too generous, they aren't even filling in the holes.

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#17

Post by jiggawatts »

jf wrote: post #5

I helped set up the first meeting between a Microsoft executive and Thomas Preston-Werner. One of the moments that stood out to me was when Robert Youngjohns (the exec) asked Tom what it would take to have GitHub move to Azure. I was surprised that Tom had a response ready, saying that IOPS were really important and that virtual disks weren’t fast enough.

Wait, are you trying to tell me that 1/100th the speed at 50x the price isn’t a great offer for Microsoft’s customers!?

Heathen lies!

Oh, wait… we have to use it? Oh, that’s terrible…

Re: Microsoft turns to AWS as GitHub faces AI capacity crunch

#20

Post by larusso »

nomel wrote: post #4
csbrooks wrote: post #2

> commits were on pace to hit 14 billion in 2026, up from 1 billion in 2025 So AI means 14x the checkins? That's not 14x features completed, but still... wow.

Seems very reasonable, from my use. I commit much more often, as checkpoints, with branch rules that prevent force pushes/deletions, so the agents can't delete anything. And, suspect MS is only counting commits, and not the eventual squashes to one commit.

And every checking runs a whole CI run?

We had it internally with our teams that open a PR to then push like 10-20 more commits but never actually interested in the client builds etc. turned out they opened the PR as a checkmark/ way to share the current state. We set cooldowns and auto cancel for the ci. And then there is the developer who uses the CI compute to run tests instead of running them locally for various reasons. We had to remind that compute isn’t for free.

Post reply on HN