Microsoft turns to AWS as GitHub faces AI capacity crunch
runtimewire.com
Microsoft turns to AWS as GitHub faces AI capacity crunch
1–10 of 83 posts
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#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.
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#3I wonder what percentage of pull requests are cascading updates caused by dependabot and multiple code review bots reviewing those PRs.
My belief is it is likely 1% or more. And likely coming in as an avalanche.
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#4> 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.
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#5I 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.
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#6Saving this for the next time someone trots out the "All cloud providers are the same" line
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#7If they pull out "Embrace. Extend. Extinguish." on AWS then I'm going to be impressed beyond mad.
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#8> 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!
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#9> 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 ?
Re: Microsoft turns to AWS as GitHub faces AI capacity crunch
#10> 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.
I am surprised it is that low. The Bun Zig-to-Rust AI port was 6755 commits in like two weeks. If you make 10 commits per working day, that is 2500/year.
While that is (hopefully) the upper end of the distribution, several companies have loudly encouraged engineers to light tokens on fire to the AI gods, so it only takes a handful of the devout to push up the average in gas town like ventures.