grit://cooking/bench/revs/left-right-count@deep-history
← cookingall benchmarksraw data

grit revs · left-right-count @deep-history

Symmetric-range left/right counts on deep-history

repo: 50,000-commit linear synthetic history; no commit graph in measured worktree · 20,000 files · 50,000 commits · 1 refs

$ grit-bench daily --only revs/left-right-count@deep-history2026-10-27 · grit 8dbc58e77 · git version 2.43.0
toolmedianminmaxrunspeak memory
git2.4 ms2.1 ms2.6 ms208.5 MB
grit4.0 ms3.8 ms4.4 ms2018 MB
grit is 1.7× slowermemory: 2.1× more
every timed run (log scale)
git
grit
1.7 ms5.5 ms
How it's measured
git runs
$ git rev-list --left-right --count HEAD~500...HEAD
grit runs
$ grit revs --left-right --count HEAD~500...HEAD
Where the time goesone extra traced run per tool, outside the timed runs
git
— not traced
grit · median run 4.0 ms
grit.repository.open
0.2 ms
grit.config.load ×2
0.1 ms
grit.pack.index.open
0.0 ms
Every day8 days
dategrit commitgitgritgrit vs gitgrit peak
2026-10-278dbc58e772.4 ms4.0 ms1.7× slower18 MB
2026-10-26c7cf2c4433.4 ms8.1 ms2.4× slower17 MB
2026-10-252824ad3912.4 ms5.7 ms2.4× slower17 MB
2026-10-24157a05dde3.3 ms6.6 ms2.0× slower17 MB
2026-10-23bddf92f863.3 ms8.6 ms2.6× slower17 MB
2026-10-224c131b9423.3 ms8.7 ms2.6× slower17 MB
2026-10-21d4844e92a3.3 ms252 ms76× slower42 MB
2026-10-204754ad0b9—not run——