cloud —

GitHub scales for 7.4B commits, adding 4M CPU cores, 160 PB storage

The platform is undergoing significant infrastructure modifications to accommodate escalating usage, as evidenced by the recent announcement from GitHub.

GitHub scales for 7.4B commits, adding 4M CPU cores, 160 PB storage

This development follows GitHub stating in August that it was experiencing 2.9 billion commits monthly, an increase from 1.4 billion recorded in April. During its GitHub Universe conference on Wednesday, the firm disclosed that it is currently processing 7.4 billion commits each month. To offer perspective on this scale, developers contributed 65 million monthly commits to the platform throughout 2024. While this level of expansion presents a favorable operational challenge, the organization has experienced recurring service interruptions. These disruptions are attributed primarily to the accelerated rate of usage growth, which the company attributes mainly to "agentic demand."

In August, GitHub's CTO, Vlad Fedorov, reported that the platform had incorporated 3 million CPU cores, largely hosted on Azure, to support this expanding workload. Subsequently, GitHub has reported augmenting its resources by adding 4 million CPU cores, alongside 160 petabytes of high-speed storage and additional processing power for GitHub Actions this year. Furthermore, the company has increased its network capacity by 50 Tb/s to ensure the smooth flow of all this data.

The announcement also served to reinforce GitHub's dedication to redesigning its platform with the aim of decoupling compute resources from storage. This subject was previously addressed earlier this month, at which point the organization noted that its internal performance evaluations indicate this novel architecture possesses the capability to deliver up to 35x greater write throughput, for instance. Jay Parikh, the EVP for Core AI at Microsoft, noted in the announcement, "Agents are changing the volume and shape of software development. Adding capacity matters, but capacity alone won’t get us there. We’ve also had to change the architecture."

The migration to Azure and its associated services presented essentially the sole viable path forward, particularly because the company's proprietary data center facilities were reaching their capacity limits. Although separating compute and storage is not an entirely novel concept in 2026, it indicates that GitHub was attempting to scale operations upon an older foundational structure.

This rapid scaling and architectural evolution reflect a broader industry trend where advanced operational demands, such as those driven by AI agents, necessitate fundamental shifts in underlying platform design and resource provisioning for major technology providers.

Why it matters

This massive infrastructure scaling highlights the intense demand driven by new development patterns like agentic workflows. For operators, this signals a critical need to monitor platform resilience as usage accelerates beyond legacy limits. The architectural shift suggests a fundamental evolution in how large-scale code hosting services operate.

Reported by thenewstack.io.

cloud

Related coverage

Elsewhere in this edition