Here's the bug report that was closed without any fix:
https://github.com/syncthing/syncthing/issues/468
And user reports of this show up pretty often:
https://github.com/syncthing/syncthing/issues/1841
https://forum.syncthing.net/t/arm-linux-cpu-usage-99-for-man...
https://github.com/syncthing/syncthing/issues/1841
A sync tool that uses on the order 2MB of RAM per GB of files or 4kB per file isn't really usable. A cheap NAS these days can easily have 6TB of RAID6 storage but it won't have 12GB of RAM. Clearly something in syncthing is keeping way too much stuff pinned in memory and the developers so far haven't focused on that. There's no apparent need for this memory usage either as there's already an on-disk database with the state of the sync folder.
I've never noticed performance issues with syncthing, excepting my old original Nexus 7 tablet which does seem to suffer a bit due to its poor hardware. I keep my photos volume (~250GB) synchronized between three desktop systems and it's never presented a problem with those.
Given that the grandparent mentions issues with larger volumes, there may be some sort of "tipping point" beyond which performance degrades, and I just have not encountered it.
Regardless I'd encourage people to give Syncthing a try. The project is under very active development and the issue the grandparent mentions may be resovled by now, and of course that issue might be environment specific and not generally applicable.
Actually it doesn't. There are some add-ons to do it but the base tool does periodic full scans.
> I've never noticed performance issues with syncthing, excepting my old original Nexus 7 tablet which does seem to suffer a bit due to its poor hardware. I keep my photos volume (~250GB) synchronized between three desktop systems and it's never presented a problem with those.
250GB between desktops with multiple GB of RAM probably works. It will soak up plenty of resources though.
>Regardless I'd encourage people to give Syncthing a try. The project is under very active development and the issue the grandparent mentions may be resovled by now, and of course that issue might be environment specific and not generally applicable.
The issue is pervasive and apparently quite deeply rooted in the way syncthing is built as it's indeed under very active development but this hasn't improved.
Stand up a dedicated server running syncthing and poof!, you have a centralized syncthing.