grit://cooking/bench/reset/sparse@sparse-240k

grit reset · sparse @sparse-240k

Sparse reset out and back, 300 visible files and 400 excluded directories

repo: 240,000-file repository with a 300-file visible sparse workset · 240,000 files · 2 commits · 3 refs

$ grit-bench daily --only reset/sparse@sparse-240k2026-10-27 · grit 8dbc58e77 · git version 2.43.0

tool	median	min	max	runs	peak memory
git	37 ms	36 ms	42 ms	20	17 MB
grit	24 ms	23 ms	27 ms	20	20 MB

grit is 1.5× fastermemory: 1.2× more

every timed run (log scale)

git

grit

19 ms53 ms

How it's measured

git runs

$ git reset --hard sparse-base && git reset --hard sparse-edited

grit runs

$ grit reset --hard sparse-base && grit reset --hard sparse-edited

checked first

before timing, git and grit were each run once and their results compared

Where the time goesone extra traced run per tool, outside the timed runs

git · median run 37 ms

cache-tree: prime_cache_tree ×2

19 ms

unpack_trees: unpack_trees ×2

13 ms

progress: Updating ×6

12 ms

index: clear_skip_worktree_from_present_files ×4

0.7 ms

index: do_write_index ×2

0.5 ms

unpack_trees: traverse_trees ×2

0.3 ms

index: do_read_index ×2

0.3 ms

cache_tree: read ×2

0.1 ms

unpack_trees: clear_ce_flags(0x00000000,0x02000000) ×2

0.1 ms

cache_tree: write ×2

0.1 ms

progress: Filtering ×2

0.0 ms

unpack_trees: clear_ce_flags(0x00080000,0x42000000) ×2

0.0 ms

grit · median run 24 ms

grit.index.write ×2

0.6 ms

grit.repository.open ×2

0.4 ms

grit.diff.tree ×2

0.3 ms

grit.index.read ×2

0.3 ms

grit.config.load ×4

0.1 ms

grit.pack.index.open ×2

0.0 ms

Every day8 days

date	grit commit	git	grit	grit vs git	grit peak
2026-10-27	8dbc58e77	37 ms	24 ms	1.5× faster	20 MB
2026-10-26	c7cf2c443	—	not run	—	—
2026-10-25	2824ad391	—	not run	—	—
2026-10-24	157a05dde	—	not run	—	—
2026-10-23	bddf92f86	—	not run	—	—
2026-10-22	4c131b942	—	not run	—	—
2026-10-21	d4844e92a	—	not run	—	—
2026-10-20	4754ad0b9	—	not run	—	—