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

grit ls-remote · all @many-refs

List all refs on many-refs bare remote vs git ls-remote

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

$ grit-bench daily --only ls-remote/all@many-refs2026-10-27 · grit 8dbc58e77 · git version 2.43.0
toolmedianminmaxrunspeak memory
git15 ms14 ms16 ms2027 MB
grit14 ms13 ms15 ms2018 MB
grit is 1.1× fastermemory: 1.5× less
every timed run (log scale)
git
grit
10 ms20 ms
How it's measured
setup
remote http://127.0.0.1:44957/remote.git served by git http-backend (git's own smart HTTP server)
git runs
$ git ls-remote http://127.0.0.1:44957/remote.git
grit runs
$ grit remote refs http://127.0.0.1:44957/remote.git
checked first
before timing, git and grit were each run once and their results compared
notes
grit trace: traced run wrote no trace to /tmp/grit-daily-trace-551938-grit.txt
Where the time goesone extra traced run per tool, outside the timed runs
git · median run 15 ms
run: git remote-http
13 ms
run: git-remote-http
12 ms
grit
— not traced
Every day8 days
dategrit commitgitgritgrit vs gitgrit peak
2026-10-278dbc58e7715 ms14 ms1.1× faster18 MB
2026-10-26c7cf2c44327 ms24 ms1.1× faster17 MB
2026-10-252824ad39116 ms15 ms1.1× faster17 MB
2026-10-24157a05dde17 ms15 ms1.1× faster17 MB
2026-10-23bddf92f8613 ms24 ms1.8× slower18 MB
2026-10-224c131b94213 ms34 ms2.7× slower18 MB
2026-10-21d4844e92a12 ms35 ms2.9× slower18 MB
2026-10-204754ad0b914 ms48 ms3.5× slower19 MB