grit://cooking/bench/add/lines@large-file
← cookingall benchmarksraw data

grit add · lines @large-file

Stage first 25k new-side lines in a 50k-line file: grit add --lines vs git apply --cached

repo: synth-10k extended by one committed 50k-line large.txt, modified into 500 hunks; file/commit counts derived from recounted base plus that setup step · 10,001 files · 1,001 commits · 800 refs

$ grit-bench daily --only add/lines@large-file2026-10-27 · grit 8dbc58e77 · git version 2.43.0
toolmedianminmaxrunspeak memory
git12 ms12 ms35 ms2010 MB
grit35 ms34 ms81 ms2033 MB
grit is 2.8× slowermemory: 3.2× more
every timed run (log scale)
git
grit
9.5 ms102 ms
How it's measured
before each run
grit-bench prepare-worktree-add-lines --git git
git runs
$ git apply --cached /tmp/grit-bench-scratch/daily-synth-10k/lines-half.patch
grit runs
$ grit add --lines 'large.txt':1-25000 -- large.txt
Where the time goesone extra traced run per tool, outside the timed runs
git · median run 12 ms
index: do_write_index
2.2 ms
index: do_read_index
0.6 ms
cache_tree: read
0.0 ms
cache_tree: write
0.0 ms
grit · median run 35 ms
grit.index.read ×4
3.2 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-278dbc58e7712 ms35 ms2.8× slower33 MB
2026-10-26c7cf2c443—fail——
2026-10-252824ad391—fail——
2026-10-24157a05dde—fail——
2026-10-23bddf92f86—fail——
2026-10-224c131b942—not run——
2026-10-21d4844e92a—not run——
2026-10-204754ad0b9—not run——