Any benchmark update with core.fsmonitor=true since git 2.37.0?

[linrongbin16]

Hi, first thanks for great work in this project.

In git 2.37.0, there is a feature file system monitor, could improve big performance. Would you please update benchmark with option core.fsmonitor=true and core.untrackedcache=true?

See: https://github.blog/2022-06-29-improve-git-monorepo-performance-with-a-file-system-monitor/

[romkatv]

That's cool! Thanks for letting me know about this feature.

I considered using inotify but decided against it because the default max_user_watches limit is much too low to be useful for gitstatusd and I cannot ask or expect users to change their system settings. There are more details in the discussion of this commit.

Do you perchance know how git solves this problem? What does it do if the repo has more than max_user_watches directories?

[linrongbin16]

no idea, just read this blog

[romkatv]

I added an explicit note to the docs saying core.fsmonitor was disable in git benchmarks. I don't intend to do anything else related to core.fsmonitor in the near future because nothing will depend on the outcome of benchmarks if I were to re-run them with core.fsmonitor set to true. Few users have git 2.37.0+ and even fewer explicitly enable core.fsmonitor, which means I cannot replace gitstatusd powerlevel10k with plain git.

That said, if you are using gitstatus explicitly (not via powerlevel10k) for its performance benefits over git, consider switching to plain git if it's fast enough with core.fsmonitor enabled.

[bluz71]

I carried out some performance tested and documented it over at issue #385