GitHub's new Git storage architecture handled 7,200 pushes/sec from 5,000 agents to one repo

krishnan · x · 2026-11-12

Krishnan breaks down GitHub's Nov 5 engineering post on its next-gen Git storage architecture, built for agentic development at scale.

Internal tests supported 5,000 concurrent agents sending 7,200 pushes per second to a single repo with fast reads — versus dozens of writes/sec on today's busiest repos.
Core insight: Git objects are immutable and content-addressed, so writers can store them without coordination; only the tiny reference update needs agreement.
Objects go to Azure Blob Storage; references use a replicated log called Ref-CAS with transactions locking only touched refs; maintenance runs off the serving path.
Next bottleneck: each push triggers extra reads from CI, deployments, and agents fetching context — downstream stages must absorb it. Limited private preview now, broader rollout early next year.

More from coding & agent