grit://cooking/bench/tag/contains@git-git

grit tag · contains @git-git

Tag --contains ref query vs git tag -l on git.git (commit-graph)

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

$ grit-bench daily --only tag/contains@git-git2026-10-27 · grit 8dbc58e77 · git version 2.43.0

tool	median	min	max	runs	peak memory
git	6.21 s	6.18 s	6.27 s	5	61 MB
grit	535 ms	531 ms	537 ms	5	73 MB

grit is 12× fastermemory: 1.2× more

every timed run (log scale)

git

grit

422 ms7.90 s

How it's measured

git runs

$ git for-each-ref refs/tags/ --contains=9c96ab987243724915fedd7ea051438b8e553e07 --format=%(refname)

grit runs

$ grit-bench refs-driver ref-query /tmp/grit-bench-scratch/daily-git-git-wt/worktree-run-git-git-wt --namespace tags --contains 9c96ab987243724915fedd7ea051438b8e553e07

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

— no phase timings for this scenario yet. They come from a traced run of each tool (GIT_TRACE2_PERF for git, GRIT_TRACE for grit).

Every day8 days

date	grit commit	git	grit	grit vs git	grit peak
2026-10-27	8dbc58e77	6.21 s	535 ms	12× faster	73 MB
2026-10-26	c7cf2c443	7.14 s	688 ms	10× faster	74 MB
2026-10-25	2824ad391	6.26 s	575 ms	11× faster	73 MB
2026-10-24	157a05dde	6.38 s	642 ms	9.9× faster	73 MB
2026-10-23	bddf92f86	—	fail	—	—
2026-10-22	4c131b942	—	not run	—	—
2026-10-21	d4844e92a	—	not run	—	—
2026-10-20	4754ad0b9	—	not run	—	—