Median p50 latency from the same benchmark harness, comparing git and Oak on identical repositories. The delta column shows how much Oak changes the wait for each operation. Run the harness yourself if you're curious oak.space/oak/benchmarks. If you find anything wrong, please let us know.
Where Oak shines most p50, standard & large profiles
scenario / operation delta p50 time
many small files · 50kinitial snapshot−95%git29,723 msoak1,412 ms
many small filesinitial snapshot−95%git2,073 msoak99.6 ms
many large binariestask snapshot−95%git443 msoak23.2 ms
wide dirty treeinitial snapshot−94%git849 msoak50.9 ms
multi-GB binariestask snapshot−94%git5,218 msoak321 ms
multi-GB binariesfull diff (info recall)−93%git3,945 msoak271 ms
many large binariesdirty snapshot−93%git362 msoak25.4 ms
multi-GB binariesdirty status−90%git1,343 msoak128 ms
Inner-loop wins the devloop you live in
scenario / operation delta p50 time
wide config refactoragent setup (clone + checkout)−89%git540 msoak58.6 ms
large asset manifestagent setup−88%git319 msoak37.7 ms
few large binariestask snapshot−82%git77.7 msoak13.9 ms
shared checkout · 8 workersparallel worker−72%git419 msoak116 ms
Where Oak has the most room to improve git-faster work
scenario / operation delta p50 time
repo init · 50k filesone-time cost+188%git14.8 msoak42.6 ms
process spawncold start+143%git22.3 msoak54.2 ms
cold dirty status · 50k filesuncached+82%git89.4 msoak163 ms
dirty status · many small filesuncached+43%git16.3 msoak23.3 ms
Oak still pays small fixed costs for cold init and process startup. The reason to use it is the loop that follows: snapshots, status checks, and large-file work can be dramatically faster across a long-running agent session.