Hello there,
I want to use FreeSync to sync my files from PC<->NAS and Laptop<->NAS so that both machines are always synced.
I've set up the synchronization on my PC, and use RealTimeSync to monitor any changes on my harddrive and adapt them to the NAS.
That's basically working, but whenever RTS detects a change it seems to scan my whole harddrive for changes, so that changing a single file takes up to 10 minutes to appear on the NAS?
Example of the problem:
1. I have several folders I'd like to keep in sync
2. Whenever I change/add/delete a single file in a single folder, FFS opens and scans all folders for changes (?)
So even when I only add a new 1kb text file in the music folder, FFS scans everything for about 10 minutes just to copy that tiny tiny file?
I hope that's a configuration error on my side?
Kind regards,
Locutus
RTS checking all directories for changes?
- Posts: 1
- Joined: 14 Dec 2021
- Posts: 2451
- Joined: 22 Aug 2012
You just discovered the disadvantage of having RTS monitor a huge amount of folders for changes and upon detecting any change run a massive sync.
Running massive syncs is normally quite OK if it is a manually started or a scheduled task (e.g. once per day), but when using RTS to initiate a sync upon detecting changes, it is much better to divide your sync in smaller (non-overlapping) syncs, and define separate RTS jobs to monitor just the folders corresponding to each individual sync.
You could for instance define a separate sync for each of your above left-right pairs (or apply some smart clustering) and define a separate RTS job for each of those syncs.
Running multiple instances of RTS in parallel on the same computer is perfectly fine, as long as there is no overlap in the folders monitored by those RTS instances.
Similarly, running multiple instances of FFS in parallel on the same computer is perfectly fine, as long as there is no overlap in the folders being synced by those FFS instances.
Running massive syncs is normally quite OK if it is a manually started or a scheduled task (e.g. once per day), but when using RTS to initiate a sync upon detecting changes, it is much better to divide your sync in smaller (non-overlapping) syncs, and define separate RTS jobs to monitor just the folders corresponding to each individual sync.
You could for instance define a separate sync for each of your above left-right pairs (or apply some smart clustering) and define a separate RTS job for each of those syncs.
Running multiple instances of RTS in parallel on the same computer is perfectly fine, as long as there is no overlap in the folders monitored by those RTS instances.
Similarly, running multiple instances of FFS in parallel on the same computer is perfectly fine, as long as there is no overlap in the folders being synced by those FFS instances.
- Posts: 4055
- Joined: 11 Jun 2019
Basically RTS just sees the change and runs a compare/sync on that FFS config, which you have set to compare all those locations at the same time. As Plerry said, break them up into individual FFS configs or chunks and create the matching RTS configs.