I don't see any reason why syncthing should use more than that. Please note that a 50% CPU utilization is hardcoded here. If the file exists and it is executable, it will use it, otherwise, it will call syncthing as usual. I’ve changed fsWatcherDelayS from the default of 10 secs to 180 secs, but this hasn’t helped. The high CPU usage lasts for several minutes after I close all programs on the remote desktop. This script will look for cpulimit in a specific route where Mageia 6 installs it. It’s at about 100 of both CPU’s on the remote Linux server (a VPS), and at least 50 of each of the 4 CPUs on the other machine (refer screenshot). CpuBench returns CPU performance as a measure of single threaded SHA-256 MiB/s. usr/bin/cpulimit -l 50 /usr/bin/syncthing -gui-address=$1 Current version number of the usage report, for acceptance purposes. The ExecStart line points to a file syncthing.sh which it is there where the cpulimit s called. Syncthing unit definition file has the following definition:ĮxecStart=/usr/bin/syncthing.sh $ I will explain how I did with syncthing, since in Mageia 6, syncthing is a service and systemd is used.
#Syncthing cpu usage how to#
In short terms, the use of cpulimit. I have already written about how to limit the CPU use in general.
So, as it is not a real-time critical task, it does not matter if files are not updated right away. I am not usually on both computers at the same time. However, if you are like me with more than 600 GB of data to have synced between your personal laptop and desktop, and you modify files frequently, you will find that syncthing needs a lot of CPU to work.Īs I see, syncing is a background task. It is especially through for road warriors as it handles two endpoints behind a NAT through its relay server.
Syncthing is a software that allows file synchronization.
0 kommentar(er)
