grit://cooking/bench/push/force-with-lease@git-git

grit push · force-with-lease @git-git

Amended commit force-with-lease push vs git push --force-with-lease

repo: Upstream git/git pinned at v2.47.0, full history · 4,525 files · 75,031 commits · 954 refs

$ grit-bench daily --only push/force-with-lease@git-git2026-10-27 · grit 8dbc58e77 · git version 2.43.0

tool	median	min	max	runs	peak memory
git	2.15 s	2.13 s	2.16 s	5	319 MB
grit	1.13 s	1.13 s	1.14 s	5	72 MB

grit is 1.9× fastermemory: 4.5× less

every timed run (log scale)

git

grit

898 ms2.72 s

How it's measured

setup

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

before each run

grit-bench prepare-network-force-with-lease --git git --bare /tmp/grit-bench-scratch/daily-remote-git-git/remote.git

git runs

$ git push --force-with-lease -q origin master

grit runs

$ grit push --force-with-lease

checked first

before timing, git and grit were each run once and their results compared

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

git · median run 2.15 s

run: git remote-http

2.12 s

run: git-remote-http

2.12 s

push: transport_push

2.12 s

transport_pu: push_refs

1.58 s

run: git send-pack

1.58 s

run: git pack-objects

521 ms

pack-objects: enumerate-objects

516 ms

transport_pu: get_refs_list

4.7 ms

pack-objects: write-pack-file

0.2 ms

pack-objects: prepare-pack

0.0 ms

grit · median run 1.13 s

grit.push

1.11 s

grit.repository.open ×3

0.4 ms

grit.config.load ×4

0.2 ms

grit.pack.index.open

0.0 ms

Every day8 days

date	grit commit	git	grit	grit vs git	grit peak
2026-10-27	8dbc58e77	2.15 s	1.13 s	1.9× faster	72 MB
2026-10-26	c7cf2c443	151 ms	1.44 s	9.5× slower	74 MB
2026-10-25	2824ad391	2.51 s	1.12 s	2.3× faster	73 MB
2026-10-24	157a05dde	2.21 s	1.18 s	1.9× faster	93 MB
2026-10-23	bddf92f86	1.70 s	656 ms	2.6× faster	78 MB
2026-10-22	4c131b942	1.61 s	626 ms	2.6× faster	78 MB
2026-10-21	d4844e92a	—	not run	—	—
2026-10-20	4754ad0b9	—	not run	—	—