When the source or destination path is a unc path (to the same NAS in this case) the ip address with the first subdirectory is shown in the "parallel file operations" dialog.
This means that when a session consists of multiple folders pairs pointing to different subdirectories on the same nas, a separate thread is used for every subdirectory.
Reading or writing to a conventional hard drive with multiple threads isn't always ideal.
Can this be changed so that only the ip address of the unc path is used in the "parallel file operations" dialog?
In that case you can still choose multiple threads, but it is also possible to read/write with only 1 thread towards the nas.
parallel file operations to unc path
- Posts: 8
- Joined: 21 Apr 2021
- Posts: 4908
- Joined: 11 Jun 2019
This isn't accurate.
Parallel threads works on base locations, not subdirectories. The location you are seeing in options is that base location, which is the root share name/location prefixed by the hostname/IP. For example, If I am syncing '\\192.168.1.202\media' with '\\192.168.1.202\storage', I get a parallel operations line for each since they are both separate shares. If I instead sync '\\192.168.1.202\media\Movies' with '\\192.168.1.202\media\TV Shows', I get a single line item labelled '\\192.168.1.202\media' for parallel operations. Changing it to only use the IP address isn't possible, because '\\x.x.x.x' isn't a valid location for data.
https://freefilesync.org/manual.php?topic=performance
Parallel threads works on base locations, not subdirectories. The location you are seeing in options is that base location, which is the root share name/location prefixed by the hostname/IP. For example, If I am syncing '\\192.168.1.202\media' with '\\192.168.1.202\storage', I get a parallel operations line for each since they are both separate shares. If I instead sync '\\192.168.1.202\media\Movies' with '\\192.168.1.202\media\TV Shows', I get a single line item labelled '\\192.168.1.202\media' for parallel operations. Changing it to only use the IP address isn't possible, because '\\x.x.x.x' isn't a valid location for data.
https://freefilesync.org/manual.php?topic=performance
- Posts: 8
- Joined: 21 Apr 2021
A separate shared folder isn't necessarily a separate drive.
FreeFileSync strives for excellent performance and is undeniably very fast, but using multiple threads to the same drive doesn't always yield performance benefits (in many cases, the opposite is true).
FreeFileSync groups folders based on their "root device."
A folder must be a valid data location, not a "root device."
FreeFileSync strives for excellent performance and is undeniably very fast, but using multiple threads to the same drive doesn't always yield performance benefits (in many cases, the opposite is true).
FreeFileSync groups folders based on their "root device."
A folder must be a valid data location, not a "root device."
- Posts: 4908
- Joined: 11 Jun 2019
1) Didn't say it wasA separate shared folder isn't necessarily a separate drive.
FreeFileSync strives for excellent performance and is undeniably very fast, but using multiple threads to the same drive doesn't always yield performance benefits (in many cases, the opposite is true).
FreeFileSync groups folders based on their "root device."
A folder must be a valid data location, not a "root device."
2) Who told you to use multiple threads for a single drive? No one here did
3A) True
3B) False. A folder can be both. For example, 'D:\' is a valid data location and a valid root device
- Posts: 8
- Joined: 21 Apr 2021
If I want to sync '\\192.168.1.202\media' with '\\192.168.1.202\storage' (both shares are on the same drive); how can I avoid using more than one thread?2) Who told you to use multiple threads for a single drive? No one here did
-
- Posts: 2978
- Joined: 22 Aug 2012
The FFS Standard Edition does not offer parallel operations.
The FFS Donation and Business Edition both offer parallel operations.
If you use the Donation or Business Edition and want to avoid using more than a single (parallel) operation, you can simply set the number of "parallel file operations" to 1 for the resource(s) involved.
The FFS Donation and Business Edition both offer parallel operations.
If you use the Donation or Business Edition and want to avoid using more than a single (parallel) operation, you can simply set the number of "parallel file operations" to 1 for the resource(s) involved.
- Posts: 4908
- Joined: 11 Jun 2019
Just leave the parallel thread settings for each location as "1"?If I want to sync '\\192.168.1.202\media' with '\\192.168.1.202\storage' (both shares are on the same drive); how can I avoid using more than one thread? vds, 03 Jan 2026, 22:532) Who told you to use multiple threads for a single drive? No one here did
If you read the linked documentation I posted, it states
When synchronizing a folder pair, FreeFileSync will use the maximum of the number of parallel operations supported by the two folders.
- Posts: 8
- Joined: 21 Apr 2021
In that case FFS is using a thread to read from '\\192.168.1.202\media' and a separate thread to read from '\\192.168.1.202\storage'.Just leave the parallel thread settings for each location as "1"? xCSxXenon, 04 Jan 2026, 20:52If I want to sync '\\192.168.1.202\media' with '\\192.168.1.202\storage' (both shares are on the same drive); how can I avoid using more than one thread? vds, 03 Jan 2026, 22:532) Who told you to use multiple threads for a single drive? No one here did
So it reads with 2 threads from \\192.168.1.202.
- Posts: 4908
- Joined: 11 Jun 2019
For comparing, yes, but it's not like the OS is traversing the entire actual file system for do this. Any modern file system is using a "table-of-contents" to provide file information. You aren't going to hurt an HDD by accessing it with multiple threads. Also, the firmware on any reputable drive is going to queue these requests, not bounce between multiple at the same time.
