(posting again from June where there were no responses at all)
I’m using syncthing-macos 1.30.0-1, and have a couple rather large (1.4M files/162GB and 1M/60GB) shares. I’m seeing really high system CPU use on an 32GB RAM intel i7 mac running Sequoia 15.7. I read that I could set GOMAXPROCS via the plist, but the syncthing-macos way of running syncthing doesn’t appear to be using the /Applications/Syncthing.app/Contents/Resources/syncthing/etc/macos-launchd/syncthing.plist file (USERNAME is not changed, and GOMAXPROCS doesn’t seem to be used).
I already have the full scan interval pushed out to once a day (fs watcher is enabled) and I’ve also got the number of shares to concurrently scan set to one to try to limit the CPU usage, but it’s still causing trouble.
Is there a different way to limit the CPU/deprioritize the IO used by Syncthing when used with the menu bar utility?
I appreciate the response, but I am asking the question in this forum after already exhausting my search of the documentation. This is in fact where I learned about parameters such as hashers, maxFolderConcurrency and GOMAXPROCS. I also spent some time trying to understand if there was something I could do to tune the database to handle these large folders, but the automatic tuning already seems to be tuned so I don’t think there is much someone such as myself could do to adjust it further.
I’d suggest to wait for a stable release of Syncthing v2 for macOS, because trying to tune up the old v1 database, which is no longer developed, isn’t really worth the time.