Skip to content
← Changelog

Rapid takes 10,527 pushes a second

Rapid, the Git engine behind every Upstream repository, now takes 10,527 pushes a second to a single repository, held for 15 minutes by 6,144 agents with no errors.

10,527 pushes a second

With 6,144 agents pushing to one repository for 15 minutes, Rapid held 10,527 pushes a second: 9.47 million pushes and no errors. In October it took about 1,800 a second.

With 384 agents cloning the same repository at the same time, it still took 10,777 pushes a second. The same 6,144 agents pushing to 64 repositories at once got 18,718.

Scaling Git for the agent era

Big repositories

We imported all of Chromium into Rapid: 55 GB, 28 million objects and 1.68 million commits. 1,000 agents in four regions pushed to it at 1,934 to 2,333 pushes a second with no errors, up from 1,220 in October.

A shallow clone of Chromium takes 46 seconds. GitHub took 107.

How it works

Each repository is a set of small objects on Cloudflare. Push lanes each own some of the branches, so two agents pushing to different branches never wait for each other. A push only succeeds once it's saved.

How Upstream Rapid works

Nothing to change

Rapid is normal Git, so git, your editor, your CI and your agents push to it the way they do today. It runs every repository on every plan, including Free. A repository nobody is pushing to sleeps and only costs its storage.