ELSEIF
Your brief EB
379 stories from 115 feeds 448 clusters Refreshed 14 minutes ago next pull 14:37

OBSERVABILITY Signal 433

Datadog's gitretriever sustained 20× CI traffic growth while holding median latency near 40 ms

Datadog built gitretriever, a Git mirror serving code to CI workloads, which now handles over 100 million weekly requests with median latency around 40 ms despite 20× traffic growth since launch.

WHY IT MATTERS

The core problem was a scaling mismatch: read traffic grows with CI jobs but write costs grow with replicas in a replicated architecture, so adding nodes made things worse. AI coding agents drove an order-of-magnitude increase in Git traffic, pushing traditional scaling approaches past their limits for organizations with large monorepos.

Written by elseif from the cluster below · every claim links back to a source

The three things worth knowing

01

gitretriever served over a billion Git requests and hundreds of terabytes of code in its first 4 months, now handling more than 100 million requests weekly.

02

Previous fixes, adding capacity, larger instances, dedicated backends, CDN proxies, failed because replication overhead scaled with node count rather than read demand.

03

AI coding agents hit Git far harder and more often than human contributors, driving an order-of-magnitude traffic increase on top of existing deployment, auditing, and security load.

THE CLUSTER

Same story, 1 feed.

ORDERED BY FIRST SEEN
datadoghq.com via Lobsters 20× the CI traffic without getting slower: How we rebuilt Git serving at Datadog Open ↗