grit://cooking/dogfood← what’s cooking
Tuesday, November 10, 2026 · Windows 11 Pro 10.0.26200

Dogfood on win-x64: Large-monorepo engineer

5 repos · 33 commands · 2 broken · 7 slow · 5 filed

Played a large-monorepo engineer on Windows: a 200k-file synthetic repo (with 4 x 40 MB and a 768 MB binary), git/git (82.8k commits) with 61k refs, plus grit serve and a library program. Everyday history work (log, blame, diff, many refs once packed, distant switch, add/commit, big-binary add) is on par with or faster than git, but Windows file-system costs are a clear gap: clean status is 2.9x git at 200k files, the first status/diff after thousands of edits is 30x git because grit opens files git never opens, a >260-char path is reported deleted, and clone of 200k files is 30-40% slower. Of 6 re-checked fixes, 4 hold (#2570, #2568, #2569, #2574) and 2 still reproduce (#2563, #2390).

os
Windows 11 Pro 10.0.26200 · x86_64
machine
self-hosted worker win-x64: Intel i5-12400, 4 logical CPUs, 16 GB RAM, NTFS, Defender real-time protection on (no exclusions)
versions
grit 0.6.0 (built from main) · main 41d768c8 · 2.55.0.windows.5
repositories5
repofilescommits.gitnotes
scratch/mono-200k (git-created clone mono-git)200,005304974 MBsynthetic 200,004 src files + 4 x 40 MB binaries, fast-imported; later a 30k-file branch and a 768 MB file
scratch/mono-200k (grit-created clone mono-grit)200,005307974 MBcloned with grit, used for grit-side measurements
git/git4,86682,797323 MBHEAD fbd2d1e765
scratch/refs-test (git/git clone + 61k branches)4,86682,797338 MB
scratch/twin, t2563, t2569, t2570———tiny hand-built repos for path edge cases and fix re-checks
commandsgrit vs. system git, wall time
commandrepogritgitgrit/gitresultnotes
grit status (clean)scratch/mono-200k517 ms176 ms2.9×ok2.9x git, 340 ms slower (#2584); sys time 1.2 s; memory equal (git = job-wide commit)
grit status --threads 1scratch/mono-200k1.29 s176 ms7.4×slow7.3x
grit status (5000 edited files, first run)scratch/mono-200k5.98 s197 ms30×slow30x (#2585); second run 464 ms
grit diff --stat (5000 edited, first run)scratch/mono-200k7.50 s1.24 s6.1×slow6x cold, ~1x warm (675 vs 682 ms)
grit add (5000 modified)scratch/mono-200k3.92 s9.19 s0.4×okgrit faster
grit commit (5000 files)scratch/mono-200k2.57 s1.93 s1.3×ok
grit switch other / main (30k files differ)scratch/mono-200k4.50 s7.95 s0.6×okfirst status after switch 941 ms vs 293 ms
grit clone (local path)scratch/mono-200k55.03 s38.91 s1.4×ok1.4x slower; checkout 50.5 s + finish 7.2 s (#2588); memory 328 MB top process vs 100 MB git tree: below the bar
grit gcscratch/mono-200k1.93 s2.05 s0.9×ok
grit add / commit / switch / gc with 768 MB filescratch/mono-200k1.71 s20.89 s0.1×okcommit 1286 vs 270 ms, switch 870 vs 3011 ms, gc 3242 vs 19491 ms; fsck clean
grit log --oneline -n 200 -- builtin/commit.cgit/git198 ms208 ms1.0×ok
grit log --json -n 1000 -- Documentationgit/git105 ms148 ms0.7×ok
grit revs --count HEADgit/git477 ms620 ms0.8×ok
grit log --follow -n 100 -- builtin/log.cgit/git181 ms329 ms0.6×ok
grit diff --stat v2.40.0 v2.45.0git/git182 ms415 ms0.4×ok
grit blame --json -- builtin/commit.cgit/git718 ms579 ms1.2×ok4 of 1993 lines attributed differently
grit blame --json -- Makefilegit/git1.45 s1.06 s1.4×ok11 of 4144 lines differ; see #2572 for timing
grit blame --json -- revision.cgit/git1.10 s1.02 s1.1×ok4 of 4833 lines differ
grit clone (local path)git/git1.83 s1.61 s1.1×ok
grit branch (61k loose refs, first read after git wrote them)scratch/refs-test236.09 s2.63 s90×slowfirst-open cost of freshly written files, see #2585; 1.8 s on repeat
grit branch --json (61k refs)scratch/refs-test2.02 s2.63 s0.8×ok
grit gc (61k loose refs)scratch/refs-test263.45 s——slowpack-refs 19.8 s, reflog-expire 239.8 s (#2585); git gc not run on this copy
grit branch (61k packed refs)scratch/refs-test86 ms406 ms0.2×ok
grit status (61k refs)scratch/refs-test66 ms117 ms0.6×ok
grit stash / stash pop (deleted file and dir)scratch/t2570———ok#2570 fixed
grit bundle verify / unbundle (unreferenced prerequisite)scratch/t2569———ok#2569 fixed
grit clone (tree with back\slash.txt)scratch/t2563———wrongwrites back/slash.txt, git rejects (#2563 reopened)
grit clone / status (trees with reserved names, trailing dot, colon, GIT~1, case collision)scratch/twin———okmatches git's rejections; collision warned
grit status / diff (path of ~380 chars)scratch/twin———wrongexisting file reported deleted (#2586)
git clone through grit servegit/git18.39 s——okfsck clean; serve peak WS 520-940 MB during a full clone
grit serve POST 12M duplicate wants (tip)scratch/small400 ms——memoryserve peak 26 MB idle -> 769 MB; stdio upload-pack ~540 MB (#2390)
grit serve POST 100k duplicate wants (non-tip)git/git265.60 s——slow1.3 ms per want (#2587)
grit-lib Repository::discover + status().run (library)scratch/mono-200k302 ms——ok4 concurrent statuses on a shared handle ~1.0 s each
worked6
  • ›add, commit, 30k-file switch, gc and large-binary add are faster than git on a 200k-file Windows repo
  • ›history queries on git/git (path-filtered log, --follow, diff between tags, revs) are on par or faster
  • ›packed 61k-ref branch listing 86 ms vs git 406 ms; branch --json is stable and bounded with -n
  • ›Windows-invalid tree entries (reserved names, trailing dot/space, a:b streams, GIT~1/.GIT. aliases) are rejected like git, case collisions are warned about
  • ›git clone through grit serve of git/git works end to end, git fsck clean; grit-written repositories fsck clean with git
  • ›grit-lib public API compiled and ran a status + threaded program without touching private modules
problems10
  • ›#2584: clean status at 200k files is 2.9x git on Windows (filed)
  • ›#2585: size-changed files are opened by status/diff; first-open costs ~4 ms per recently written file for binaries outside Program Files (filed)
  • ›#2586: >260-char path written by clone but reported as deleted (filed)
  • ›#2587: non-tip duplicate wants cost 1.3 ms each in grit serve (filed)
  • ›#2588: 200k-file clone 30-40% slower than git, 7 s finish phase (filed)
  • ›#2563 and #2390 still reproduce (reopened through verify_fix)
  • ›Not filed: grit clone of a repo whose HEAD points to a missing branch only prints a warning and checks nothing out (git also warns); fine
  • ›Not filed: grit gc / switch peak working set ~1 GB with a 768 MB blob; mostly mapped pack pages, my Windows measurement cannot separate it from private memory
  • ›Not filed: StatusOptions.pathspecs is Vec<String> where API conventions ask for Pathspec; grit-examples lacks a realistic status/tree-walk example (api nit)
  • ›Not filed: grit init defaults to 'master' while the lib docs example expects 'main' (docs/example mismatch, minor)
bugs filed5
#2584 #2585 #2586 #2587 #2588already reported: #2276 #2566 #2173 #2462 #2467 #2572
next time
  • ›Install a code-signed grit.exe under C:\Program Files and re-run #2585 to separate the signature/location penalty from grit's own opens; also try on a Dev Drive
  • ›Measure true RSS (private working set) for gc/switch with large blobs instead of peak working set
  • ›Re-run #2584 with core.fsmonitor/untracked cache on both sides and on 500k-1M files
  • ›Directory renames at 50k-150k paths for merge/pick/rebase (not reached this session)
  • ›grit rebase/history edits at 200k files, and concurrent commit/switch sessions through grit-lib with a custom ObjectStore
  • ›Push of a 100k-file commit and 20 concurrent clones against grit serve with server RSS sampling
  • ›linux kernel clone for blame -C -M and log --follow