Tune Syncthing for low-resource devices

Ideas
1

I’ve been following this guide. Enabling every option mentioned in the tuning for low resource devices section is probably overkill/too much of a compromise, but I think the defaults in MUOS could be improved upon. At the least, I would reducemaxFolderConcurrencyto 1. Configuration Tuning — Syncthing documentation

A more brute-force approach that might really be needed for muos devices might be to set the environment variable GOMAXPROCS

This environment variable can be used to control the maximum number number concurrently running threads Syncthing uses. Setting it to 1 (or any number lower than your actual number of cores) will reduce the amount of CPU used by Syncthing at any given moment.

Here are changes I personally made and like:

General options:

progressUpdateIntervalSSet to 20 to decrease progress updates.

maxFolderConcurrencySet to 1 to sync folders sequentially, reducing the peak memory usage.

maxConcurrentIncomingRequestKiB Set to 32768 KiB (32 MiB) to reduce the amount of memory used for buffering responses to incoming requests.

1 Like
2

The obvious disadvantage of tuning in this way is that initial syncs might take longer. I’m not actually sure that will be true though, because it seems like current settings cause a choking bottleneck.