The new release adds a builtin file watcher for macOS and Windows to improve git status performance. Activating the watcher per repository works like this: git config core.fsmonitor true.
Im still prefering FB’s watchman over the current IPC implementation.
Not only that the config supports Linux, watchman also uses multiple different mechanism to watch the file instead of just 1. It’s battle tested against FB’s monorepo and is critically depended by many dev tools in facebook.
Finally, the watchman daemon provides SDK for other tools to integrate with. So I see no benefit in switching to this IPC implementation if you have already been using watchman.
The new release adds a builtin file watcher for macOS and Windows to improve
git statusperformance. Activating the watcher per repository works like this:git config core.fsmonitor true.Note that activating
core.fsmonitormight result in the following warning message:warning: Empty last update token.Tangential question: what would be the kind of workloads where NTFS would be an optimal choice ? File operations seem to be so costly on it.
On windows it’s the only filesystem that offers journaling.
There was some cool advances for the time with regards to security and file compression when the disk gets close to full.
These days modern Linux filesystems obsolete it quite clearly.
HFS+ on MacOS was in the same circumstances which is why Apple is working on APFS and Microsoft is working on ReFS.
APFS is the default file system on all devices sold by Apple today.
I didn’t see much performance boost on one of our large repos at work. Makes me think most of the time spent by
git statusis due to AV software.Im still prefering FB’s watchman over the current IPC implementation.
Not only that the config supports Linux, watchman also uses multiple different mechanism to watch the file instead of just 1. It’s battle tested against FB’s monorepo and is critically depended by many dev tools in facebook.
Finally, the watchman daemon provides SDK for other tools to integrate with. So I see no benefit in switching to this IPC implementation if you have already been using watchman.
Sparse index going GA should be a big deal for a lot of orgs with giant monorepo.