grit://cooking/bench/status/clean@deep-tree
← cookingall benchmarksraw data

grit status · clean @deep-tree

Clean worktree on deep-tree: grit status vs git status -s

repo: 5,000 files nested across 30–40 directory levels · 5,000 files · 300 commits · 60 refs

$ grit-bench daily --only status/clean@deep-tree2026-10-27 · grit 8dbc58e77 · git version 2.43.0
toolmedianminmaxrunspeak memory
git1.06 s1.04 s1.11 s538 MB
grit642 ms627 ms660 ms570 MB
grit is 1.6× fastermemory: 1.8× more
every timed run (log scale)
git
grit
498 ms1.40 s
How it's measured
before each run
grit-bench prepare-worktree-status-clean --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 1.06 s
status: untracked
959 ms
dir: read_directory
959 ms
index: preload
57 ms
index: do_read_index
21 ms
cache_tree: read
20 ms
status: index
2.0 ms
index: name-hash-init
1.1 ms
unpack_trees: unpack_trees
0.9 ms
unpack_trees: traverse_trees
0.8 ms
index: refresh
0.2 ms
status: worktrees
0.1 ms
diff: setup ×2
0.0 ms
diff: write ×2
0.0 ms
status: print
0.0 ms
grit · median run 642 ms
grit.status.scan
632 ms
grit.index.read
19 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-278dbc58e771.06 s642 ms1.6× faster70 MB
2026-10-26c7cf2c4432.35 s1.40 s1.7× faster75 MB
2026-10-252824ad3911.15 s709 ms1.6× faster69 MB
2026-10-24157a05dde1.07 s665 ms1.6× faster70 MB
2026-10-23bddf92f861.12 s1.20 s1.1× slower67 MB
2026-10-224c131b9421.16 s1.21 spar69 MB
2026-10-21d4844e92a1.06 s1.12 s1.1× slower68 MB
2026-10-204754ad0b91.21 s1.26 spar67 MB