← All stories
● Covered by 2 sources · 2 reportsMedium impact2 neutral

GitHub Adds 4M CPU Cores and 160 PB Storage to Handle 7.4B Monthly Commits

🔄 Updated 8d ago — new reporting from Tom's Hardware
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • GitHub reached 7.4 billion monthly commits in September.
  • Added 4 million CPU cores and 160 petabytes of storage.
  • Increased network capacity by 50 Tb/s.
  • Rearchitecting platform to separate compute and storage.
  • Code commits grew sixfold year-over-year.
  • Merged pull requests quadrupled year-over-year.
  • Agentic AI initiates over 40% of pull requests.

Surge in Commit Volume

GitHub announced a substantial increase in platform activity, reaching 7.4 billion commits in September. This marks a significant jump from 2.9 billion commits reported in August and 1.4 billion in April. The company attributes this rapid growth primarily to 'agentic demand,' indicating increased automated activity on the platform.

Infrastructure Expansion

To accommodate the escalating demand, GitHub has expanded its core infrastructure. This year, the platform added 4 million CPU cores, primarily on Azure, along with 160 petabytes of high-speed storage. Additionally, GitHub increased its network capacity by 50 Tb/s to manage the increased data flow and provided more compute power for GitHub Actions.

Architectural Shift

GitHub is rearchitecting its platform to separate compute and storage, a strategy it first discussed earlier this month. This new architecture is projected to deliver up to 35 times higher write throughput based on internal benchmarks. Jay Parikh, EVP for Core AI at Microsoft, stated that while adding capacity is necessary, architectural changes are also crucial for handling the evolving nature and volume of software development.

Addressing Legacy Foundations

The move to separate compute and storage indicates GitHub's transition from a legacy foundation that struggled to scale with current demands. Migrating to Azure and its services became a necessary step, especially as GitHub's own data centers reached capacity limits.

Updates

🕒 2026-10-29 · new reporting from Tom's Hardware
  • Code commits grew sixfold year-over-year.
  • Merged pull requests quadrupled year-over-year.
  • Agentic AI initiates over 40% of pull requests.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 07

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

How outlets covered it

GitHub expanded its infrastructure with 4 million CPU cores, 160 petabytes of storage, and 50 Tb/s of networking capacity to manage a massive increase in AI-generated code. Code commits grew sixfold and merged pull requests quadrupled year-over-year, driven by agentic AI, which now initiates over 40% of pull requests.

GitHub reported 7.4 billion commits in September, a significant increase from 2.9 billion in August, driven by 'agentic demand.' To manage this growth, GitHub added 4 million CPU cores, 160 petabytes of storage, and 50 Tb/s of network capacity, while also rearchitecting its platform to separate compute and storage.