What did you do before the bug happened? (Steps to reproduce your issue) Enabled core.fsmonitor in ~/.gitconfig What did you expect to happen? (Expected behavior) Faster git status, or at the very least not slower. What happened instead? (Actual behavior) Significantly slower git status. What's different between what you expected and what actually happened? With the fsmonitor git status takes like 2-8s when normally it's under 1s, I expected it to be faster than normal. Anything else you want to add: I've tried apple's git (used to generate this report) and the one from homebrew (2.38.0). The repo doesn’t seem to matter much, some are a bit faster than others, but they’re all really slow. I tried to track down the slowness using trace2.perfTarget and from that it seemed to spend a lot of time doing fsync. [System Info] git version: git version 2.37.0 (Apple Git-136) cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Darwin 21.6.0 Darwin Kernel Version 21.6.0: Mon Aug 22 20:17:10 PDT 2022; root:xnu-8020.140.49~2/RELEASE_X86_64 x86_64 compiler info: clang: 14.0.0 (clang-1400.0.29.201) libc info: no libc information available $SHELL (typically, interactive shell): /usr/local/bin/bash [Enabled Hooks]
