grit://cooking/bench/add/modified@big-blobs
← cookingall benchmarksraw data

grit add · modified @big-blobs

Stage ~1% modified paths: grit add -- <paths> vs git add -- <paths>

repo: 200 paths with large binary blobs and multiple blob revisions · 200 files · 120 commits · 40 refs

$ grit-bench daily --only add/modified@big-blobs2026-10-27 · grit 8dbc58e77 · git version 2.43.0
toolmedianminmaxrunspeak memory
git213 ms212 ms216 ms1078 MB
grit115 ms106 ms118 ms1088 MB
grit is 1.9× fastermemory: 1.1× more
every timed run (log scale)
git
grit
84 ms272 ms
How it's measured
before each run
grit-bench prepare-worktree-add --git git
git runs
$ set -eu
if [ -s /tmp/grit-bench-scratch/daily-big-blobs/.grit-bench-worktree-paths ]; then
  tr '\n' '\0' < /tmp/grit-bench-scratch/daily-big-blobs/.grit-bench-worktree-paths | xargs -0 git add -- > /dev/null 2>&1
fi
grit runs
$ set -eu
if [ -s /tmp/grit-bench-scratch/daily-big-blobs/.grit-bench-worktree-paths ]; then
  tr '\n' '\0' < /tmp/grit-bench-scratch/daily-big-blobs/.grit-bench-worktree-paths | xargs -0 grit add -- > /dev/null 2>&1
fi
Where the time goesone extra traced run per tool, outside the timed runs
git · median run 213 ms
index: do_write_index
0.1 ms
index: do_read_index
0.1 ms
dir: read_directory
0.0 ms
cache_tree: read
0.0 ms
index: name-hash-init
0.0 ms
cache_tree: write
0.0 ms
grit · median run 115 ms
grit.repository.open
0.2 ms
grit.index.write
0.2 ms
grit.config.load ×2
0.1 ms
grit.index.read
0.1 ms
grit.pack.index.open
0.0 ms
Every day8 days
dategrit commitgitgritgrit vs gitgrit peak
2026-10-278dbc58e77213 ms115 ms1.9× faster88 MB
2026-10-26c7cf2c443290 ms275 ms1.1× faster87 MB
2026-10-252824ad391234 ms132 ms1.8× faster86 MB
2026-10-24157a05dde226 ms545 ms2.4× slower155 MB
2026-10-23bddf92f86223 ms412 ms1.8× slower156 MB
2026-10-224c131b942220 ms400 ms1.8× slower155 MB
2026-10-21d4844e92a214 ms462 ms2.2× slower154 MB
2026-10-204754ad0b9242 ms444 ms1.8× slower155 MB