grit://cooking/bench/remote/rename@many-refs

grit remote · rename @many-refs

Rename remote with many packed tracking refs vs git remote rename

repo: 10,000 packed refs · 200 files · 1,000 commits · 10,000 refs

$ grit-bench daily --only remote/rename@many-refs2026-10-27 · grit 8dbc58e77 · git version 2.43.0

tool	median	min	max	runs	peak memory
git	55.38 s	55.38 s	55.38 s	1	9.2 MB
grit	3.19 s	3.19 s	3.19 s	1	81 MB

grit is 17× fastermemory: 8.8× more

every timed run (log scale)

git

grit

2.53 s69.72 s

How it's measured

setup

remote http://127.0.0.1:38513/remote.git served by git http-backend (git's own smart HTTP server)

before each run

set -eu cd /tmp/grit-bench-scratch/daily-remote-remote-rename-many-refs/remote.git-campaign-push-client && (git remote rename upstream origin 2>/dev/null || true)

git runs

$ git remote rename origin upstream

grit runs

$ grit remote rename origin upstream

Where the time goesone extra traced run per tool, outside the timed runs

git

— not traced

grit · median run 3.19 s

grit.repository.open

0.3 ms

grit.config.load ×3

0.2 ms

Every day8 days

date	grit commit	git	grit	grit vs git	grit peak
2026-10-27	8dbc58e77	55.38 s	3.19 s	17× faster	81 MB
2026-10-26	c7cf2c443	—	fail	—	—
2026-10-25	2824ad391	—	fail	—	—
2026-10-24	157a05dde	—	fail	—	—
2026-10-23	bddf92f86	—	not run	—	—
2026-10-22	4c131b942	—	not run	—	—
2026-10-21	d4844e92a	—	not run	—	—
2026-10-20	4754ad0b9	—	not run	—	—