I used the update method to put new/modified versions of files from LHS folder base to the RHS folder base today. I noticed that FFS scanned the *entire* RHS file structure during this operation. Would it not be simpler and faster to scan the LHS first and then restrict the RHS scan to the file/folder entries from the LHS scan?! Especially when the RHS file structure might be very large. Just a suggestion.
Love the software!
Redundant RHS scan during Update?
- Posts: 1
- Joined: 11 Jun 2020
-
- Posts: 2451
- Joined: 22 Aug 2012
For the Update sync variant this indeed seems to be a possibility.
It would however make the scan sync variant specific; for all three other variants a full scan of both sides is required to determine the sync actions. This is probably the reason Zenju decided for the present approach.
You can however possibly use the Exclude Filter, by excluding one or more of the larger folders (incl. their subfolders and files) in the RHS folder that will never be part of the sync.
Those folders will then alos be skipped for scanning during the Compare phase.
Alternatively, it may be more convenient to only Include the folders that need to be synced.
It would however make the scan sync variant specific; for all three other variants a full scan of both sides is required to determine the sync actions. This is probably the reason Zenju decided for the present approach.
You can however possibly use the Exclude Filter, by excluding one or more of the larger folders (incl. their subfolders and files) in the RHS folder that will never be part of the sync.
Those folders will then alos be skipped for scanning during the Compare phase.
Alternatively, it may be more convenient to only Include the folders that need to be synced.
