4 ms·
I’m quite confused as to what you actually shipped to your developers to increase performance. This config option is a great place to start, but it would be gre
by dundarious 6y ago
I’m quite confused as to what you actually shipped to your developers to increase performance. This config option is a great place to start, but it would be great if that were clearer, so that others could follow suit.
- ublaze 6y agoWe shipped a wrapper that tweaks git configs and logs metrics, and a custom fsmonitor hook that was slightly faster than the stock one. We also ensured watchman was installed on developers laptops. And we made a few changes to Git to fix bugs (for example, `git stash` wasn't using fsmonitor data, so it was slow).
- dundarious 6y agoIt would be great to have a listing of those config tweaks, even if with caveats attached, such as “causes issues with submodule”. I don’t want to seem demanding, but it’s such a tantalizing article without this info :)
- ublaze 6y agoSure. core.fsmonitor is set to our custom fsmonitor (this causes issues with submodules, at least on 2.24) core.untrackedCache true We use index version 4 And a slight hack: our wrapper sets GIT_FORCE_UNTRACKED_CACHE = 1. This forces `git status` to write the untracked cache if it notices a difference. I was too lazy to add a patch to configure that.
- dundarious 6y agoWonderful, thank you!