grit://cooking/bench/status/renamed@synth-10k
← cookingall benchmarksraw data

grit status · renamed @synth-10k

Staged rename in status: grit status vs git status -s after git mv

repo: 10,000-file synthetic repository; canonical cached shape, scenario variants documented by the runner · 10,000 files · 1,000 commits · 800 refs

$ grit-bench daily --only status/renamed@synth-10k2026-10-27 · grit 8dbc58e77 · git version 2.43.0
toolmedianminmaxrunspeak memory
git6.6 ms6.1 ms7.7 ms809.1 MB
grit7.7 ms7.1 ms8.4 ms8020 MB
grit is 1.2× slowermemory: 2.2× more
every timed run (log scale)
git
grit
4.9 ms11 ms
How it's measured
before each run
grit-bench prepare-worktree-mv-file --git git
git runs
$ git status -s
grit runs
$ grit status
Where the time goesone extra traced run per tool, outside the timed runs
git · median run 6.6 ms
status: untracked
2.2 ms
dir: read_directory
2.2 ms
index: preload
2.2 ms
index: do_read_index
0.6 ms
index: name-hash-init
0.2 ms
index: refresh
0.2 ms
status: index
0.2 ms
status: worktrees
0.1 ms
unpack_trees: unpack_trees
0.1 ms
cache_tree: read
0.0 ms
diff: setup ×2
0.0 ms
diff: write ×2
0.0 ms
unpack_trees: traverse_trees
0.0 ms
status: print
0.0 ms
grit · median run 7.7 ms
grit.status.scan
5.5 ms
grit.index.read
0.9 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-278dbc58e776.6 ms7.7 ms1.2× slower20 MB
2026-10-26c7cf2c44318 ms16 ms1.1× faster20 MB
2026-10-252824ad3917.5 ms9.8 ms1.3× slower20 MB
2026-10-24157a05dde7.2 ms9.2 ms1.3× slower18 MB
2026-10-23bddf92f8611 ms15 ms1.3× slower19 MB
2026-10-224c131b94221 ms26 ms1.3× slower18 MB
2026-10-21d4844e92a7.1 ms17 ms2.4× slower18 MB
2026-10-204754ad0b9—not run——