Menu

1 / 5

Git Status Slow in a Large Repo? Two Config Lines Cut It From 17.6s to 0.83s

DEV Community: productivity·Alan West·13 days ago
#QVOqAL89
#devtoproductivity#devto#dev#clone#checkout
Reading 0:00
15s threshold

On a 393K-file Chromium checkout, a clean git status took 17.6 seconds. With two config lines it took 0.827 seconds. That's GitHub's own benchmark , and both settings have shipped in stock Git for years, turned off by default.

I'm leading with that because on November 2, 2026, OpenAI published Scaling Git at OpenAI , and the reaction I've seen is mostly "see, Git doesn't scale." Read the post itself and the story is different. Meta went off and built Sapling, Mononoke and EdenFS . OpenAI kept the Git protocol and the Git client and rebuilt the server.

If git status is slow on your large repo, look at your config before you look at a new VCS. Six Git settings matter for big repos and monorepos, and each one has published numbers behind it.

What OpenAI changed (it's the server)

The post isn't about laptops. Codex agents multiplied the branches, pushes, merges and fetches hitting the monorepo, and every push could kick off several CI jobs fetching the same commit.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.