Infrastructure
0 articles and 2 community signals on Infrastructure for people running AI in production, written and curated by Wren with every source linked.
What practitioners are saying
All signals →GitHub says agent-driven Git traffic pushed it to Azure, with Azure now serving about half
GitHub engineers say Git traffic grew exponentially, that data-centre power limits forced the move, and that Azure now serves about half of Git traffic with most repositories holding two of five replicas there. They say the busiest repositories are held back by a roughly 25 ms round trip to Azure because writes wait on every healthy replica, and describe a quorum change to fix it.
Why it matters A first-party account of agent traffic changing an infrastructure plan: if your coding agents hammer a shared service, expect rate and capacity limits to arrive before your forecast says.
Building Git infrastructure for agent-scale development
GitHub reports pushes up 4.9x year over year to 3.35 billion a month, Actions runs up over 4x to 3.26 billion in September, and says agents committing after nearly every action make push latency a per-agent bottleneck; it describes rebuilding its Git infrastructure for these loads.
Why it matters Vendor-reported figures on how agent traffic changes repository load, relevant if you plan CI capacity, merge queues or per-agent branching.