4 ms·

I love syncthing, but one thing which I think it does not quite do right is - on my Windows desktop each time desktop is resumed from sleep or reboot, it perfor

I love syncthing, but one thing which I think it does not quite do right is - on my Windows desktop each time desktop is resumed from sleep or reboot, it performs full sync by scanning everything. It takes all the CPU for awhile until syncthing settles down. I am not sure if this problem is Windows specific though.

karlicoss 5y ago
There is a restartOnWakeup which is true by default, seems like it's the one? There is also a setLowPriority setting which I believe should prevent it from taking all CPU, but not sure since never had such problem on Linux. https://docs.syncthing.net/users/config.html https://docs.syncthing.net/users/config.html
- ComputerGuru 5y ago
  Low priority stops it from consuming all cpu when there is contention for the cpu, but not when the pc is otherwise idle.
  - TuringTest 5y ago
    If the PC is otherwise idle, why is it a problem that a process takes all CPU if it needs it?
    - ComputerGuru 5y ago
      Battery consumption, fan noise, heat, etc.
    - TeMPOraL 5y ago
      'gnufied mentioned a Windows desktop so the biggest problem would be noise, but what about portable Windows devices? My secondary computer is a Windows 2-in-1. It's frequently running on battery power, and during that time, I often wake it up, check something, and put it back to sleep - all in a minute or less, repeated a dozen times an hour. If each time I turn the screen on Syncthing is going to run at full throttle for a minute or more, it'll drastically cut the effective work-on-battery time. (This article popping up on HN reminded me that I wanted to check Syncthing out. But what 'gnufied described is a total deal breaker for me, so I'm not going to bother for now.)
    - hectormalot 5y ago
      In my case: Battery on laptops
Sophistifunk 5y ago
My guess: Sleep/resume breaks continuity across file change watchers, and it's a requirement to scan everything in case it's been modified.
knz_ 5y ago
Even worse if you're trying to sync a file that might be actively changed while syncing - syncthing will reread the entire file as soon as only a few kilobytes are changed. On a file >10GiB this quickly leads to a death spiral of IO and CPU starvation.
- mekster 5y ago
  That's why I run a custom backup script every 5 minutes to simply rsync my data over instead of realtime syncing.
ElCapitanMarkla 5y ago
I had this same issue, ended up uninstalling it all because I couldn't figure how to address it.

karlicoss 5y ago

There is a restartOnWakeup which is true by default, seems like it's the one? There is also a setLowPriority setting which I believe should prevent it from taking all CPU, but not sure since never had such problem on Linux. https://docs.syncthing.net/users/config.html https://docs.syncthing.net/users/config.html

ComputerGuru 5y ago
Low priority stops it from consuming all cpu when there is contention for the cpu, but not when the pc is otherwise idle.
- TuringTest 5y ago
  If the PC is otherwise idle, why is it a problem that a process takes all CPU if it needs it?
  - ComputerGuru 5y ago
    Battery consumption, fan noise, heat, etc.
  - TeMPOraL 5y ago
    'gnufied mentioned a Windows desktop so the biggest problem would be noise, but what about portable Windows devices? My secondary computer is a Windows 2-in-1. It's frequently running on battery power, and during that time, I often wake it up, check something, and put it back to sleep - all in a minute or less, repeated a dozen times an hour. If each time I turn the screen on Syncthing is going to run at full throttle for a minute or more, it'll drastically cut the effective work-on-battery time. (This article popping up on HN reminded me that I wanted to check Syncthing out. But what 'gnufied described is a total deal breaker for me, so I'm not going to bother for now.)
  - hectormalot 5y ago
    In my case: Battery on laptops

Sophistifunk 5y ago

My guess: Sleep/resume breaks continuity across file change watchers, and it's a requirement to scan everything in case it's been modified.

knz_ 5y ago

Even worse if you're trying to sync a file that might be actively changed while syncing - syncthing will reread the entire file as soon as only a few kilobytes are changed. On a file >10GiB this quickly leads to a death spiral of IO and CPU starvation.

mekster 5y ago
That's why I run a custom backup script every 5 minutes to simply rsync my data over instead of realtime syncing.

ElCapitanMarkla 5y ago

I had this same issue, ended up uninstalling it all because I couldn't figure how to address it.