Scanning file by file remotely are so expensive. Can you please make something that links 2 FreeFileSync as server and client, so that both can compare files between them.
Maybe, sending request to scan to the other side, and then receive a list with date/time and sizes, then compare locally.
Thank you
Request for Remote Syncing
- Posts: 1
- Joined: 30 Dec 2021
-
- Posts: 2451
- Joined: 22 Aug 2012
> Scanning file by file remotely are so expensive.
Not sure what you mean. Expensive in what sense?
Taking a lot of time? High provider cost?
For every sync, there is always just one FFS instance active.
This instance may run on the machine on which also one or more of the left and/or right side sync locations reside, or on a machine different from where the left and right locations reside.
In both cases, one may consider the machine running the FFS instance the FFS server, and all other locations involved in the sync to be clients.
If you do a comparison (=scan?) by file content, then every entire file needs to be transferred from the "client" to the "server" to be compared there. So this is inherently slow and requires the transfer of a lot of data.
If you compare by file date and size, FFS only requests that data from the "client" to be sent to the "server", but (still) does so on a per-file basis, as that is the present architecture of FFS.
Any "slowness" in a comparison based on file date and time is likely caused by a substantial overhead in the handshake between "server" and "client", introducing latencies.
If you have the FFS donation edition, using multiple parallel file operations (Comparison window, right top) should then speed up the process.
Not sure what you mean. Expensive in what sense?
Taking a lot of time? High provider cost?
For every sync, there is always just one FFS instance active.
This instance may run on the machine on which also one or more of the left and/or right side sync locations reside, or on a machine different from where the left and right locations reside.
In both cases, one may consider the machine running the FFS instance the FFS server, and all other locations involved in the sync to be clients.
If you do a comparison (=scan?) by file content, then every entire file needs to be transferred from the "client" to the "server" to be compared there. So this is inherently slow and requires the transfer of a lot of data.
If you compare by file date and size, FFS only requests that data from the "client" to be sent to the "server", but (still) does so on a per-file basis, as that is the present architecture of FFS.
Any "slowness" in a comparison based on file date and time is likely caused by a substantial overhead in the handshake between "server" and "client", introducing latencies.
If you have the FFS donation edition, using multiple parallel file operations (Comparison window, right top) should then speed up the process.
