grit://cooking/bench/switch/delete-heavy@wide-48k

grit switch · delete-heavy @wide-48k

Switch to a branch deleting 2000 files in 20 dirs of a 48k-file tree and back: grit switch vs git switch

repo: 48,000-file baseline tree; other branch deletes 2,000 files · 48,000 files · 2 commits · 3 refs

$ grit-bench daily --only switch/delete-heavy@wide-48k2026-10-27 · grit 8dbc58e77 · git version 2.43.0

tool	median	min	max	runs	peak memory
git	109 ms	100 ms	122 ms	53	22 MB
grit	123 ms	118 ms	141 ms	53	34 MB

grit is 1.1× slowermemory: 1.6× more

every timed run (log scale)

git

grit

80 ms178 ms

How it's measured

before each run

grit-bench prepare-switch --git git

git runs

$ git switch -q bench-b && git switch -q bench-a

grit runs

$ grit switch bench-b && grit switch bench-a

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

git · median run 109 ms

unpack_trees: unpack_trees ×2

53 ms

index: do_write_index ×2

19 ms

index: preload ×4

18 ms

unpack_trees: traverse_trees ×2

11 ms

index: refresh ×2

6.1 ms

index: do_read_index ×2

5.0 ms

cache_tree: update ×2

1.1 ms

cache_tree: read ×2

0.2 ms

cache_tree: write ×2

0.1 ms

grit · median run 123 ms

grit.index.write ×2

23 ms

grit.index.read ×2

7.3 ms

grit.repository.open ×2

0.4 ms

grit.config.load ×6

0.2 ms

grit.pack.index.open ×3

0.1 ms

Every day8 days

date	grit commit	git	grit	grit vs git	grit peak
2026-10-27	8dbc58e77	109 ms	123 ms	1.1× slower	34 MB
2026-10-26	c7cf2c443	226 ms	199 ms	1.1× faster	33 MB
2026-10-25	2824ad391	132 ms	139 ms	1.1× slower	33 MB
2026-10-24	157a05dde	129 ms	130 ms	par	34 MB
2026-10-23	bddf92f86	—	not run	—	—
2026-10-22	4c131b942	—	not run	—	—
2026-10-21	d4844e92a	—	not run	—	—
2026-10-20	4754ad0b9	—	not run	—	—