grit://cooking/bench/remote/show@many-refs
← cookingall benchmarksraw data

grit remote · show @many-refs

Remote show on many-refs client vs git remote show origin

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

$ grit-bench daily --only remote/show@many-refs2026-10-27 · grit 8dbc58e77 · git version 2.43.0
toolmedianminmaxrunspeak memory
git34 ms33 ms48 ms8030 MB
grit20 ms19 ms28 ms8019 MB
grit is 1.7× fastermemory: 1.5× less
every timed run (log scale)
git
grit
15 ms60 ms
How it's measured
setup
remote http://127.0.0.1:41403/remote.git served by git http-backend (git's own smart HTTP server)
git runs
$ git remote show origin
grit runs
$ grit remote show origin
Where the time goesone extra traced run per tool, outside the timed runs
git · median run 34 ms
run: git remote-http
31 ms
run: git-remote-http
30 ms
grit · median run 20 ms
grit.repository.open
0.2 ms
grit.config.load ×2
0.1 ms
Every day8 days
dategrit commitgitgritgrit vs gitgrit peak
2026-10-278dbc58e7734 ms20 ms1.7× faster19 MB
2026-10-26c7cf2c44373 ms33 ms2.2× faster19 MB
2026-10-252824ad39138 ms22 ms1.7× faster19 MB
2026-10-24157a05dde41 ms24 ms1.7× faster18 MB
2026-10-23bddf92f8634 ms518 ms15× slower17 MB
2026-10-224c131b942—not run——
2026-10-21d4844e92a—not run——
2026-10-204754ad0b9—not run——