GitHub moves its busiest Git repositories to Azure with per-reference write quorum
Overview
GitHub says it has moved 99.99999% of its Git repositories to Azure, and that the busiest remaining ones were held back by cross-region latency.
In an X post from @github, GitHub describes a new write path that serializes writes per reference instead of per repository. GitHub says this raised write throughput 3–4x in internal tests. The change also enables stateless Azure Blob Storage replicas that GitHub says scale reads independently.
Written by AI from the articles below · updated Oct 21, 3:00 PM ET
Check the sources:
Article timeline
The articles in this story. Times are ET.
GitHub@githubOfficialGitHub explains how it moved its busiest Git repos to AzureAIGitHub says it has moved 99.99999% of its Git repositories to Azure, with the busiest remaining ones held back by cross-region latency. It describes a new write path that serializes writes per reference instead of per repository, which it says raised write throughput 3–4x in internal tests. The change also enables stateless Azure Blob Storage replicas that scale reads independently.
Heat Trend
Not enough continuous observations to show a trend yet.