grit://cooking/bench/push/incremental@git-git
← cookingall benchmarksraw data

grit push · incremental @git-git

Incremental push vs git push

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

$ grit-bench daily --only push/incremental@git-git2026-10-27 · grit 8dbc58e77 · git version 2.43.0
toolmedianminmaxrunspeak memory
git2.15 s2.13 s2.16 s5319 MB
grit1.46 s1.44 s1.48 s587 MB
grit is 1.5× fastermemory: 3.7× less
every timed run (log scale)
git
grit
1.15 s2.72 s
How it's measured
setup
remote http://127.0.0.1:43367/remote.git served by git http-backend (git's own smart HTTP server)
before each run
grit-bench prepare-network-push --git git --bare /tmp/grit-bench-scratch/daily-remote-git-git/remote.git
git runs
$ git push -q origin master
grit runs
$ grit push
checked first
before timing, git and grit were each run once and their results compared; the starting state is verified before every timed run; the result is verified after every timed run
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
507 ms
pack-objects: enumerate-objects
499 ms
transport_pu: get_refs_list
5.0 ms
pack-objects: prepare-pack
2.1 ms
pack-objects: write-pack-file
0.7 ms
grit · median run 1.46 s
grit.push
1.44 s
grit.repository.open ×3
0.5 ms
grit.config.load ×4
0.2 ms
grit.pack.index.open
0.0 ms
Every day8 days
dategrit commitgitgritgrit vs gitgrit peak
2026-10-278dbc58e772.15 s1.46 s1.5× faster87 MB
2026-10-26c7cf2c443170 ms2.05 s12× slower90 MB
2026-10-252824ad3912.44 s1.76 s1.4× faster85 MB
2026-10-24157a05dde2.31 s1.76 s1.3× faster135 MB
2026-10-23bddf92f861.64 s7.6 ms217× faster26 MB
2026-10-224c131b9421.64 s8.6 ms190× faster25 MB
2026-10-21d4844e92a1.56 s5.5 ms287× faster18 MB
2026-10-204754ad0b91.84 s8.0 ms230× faster17 MB