Hi
And the number of files is...? Bear in mind the number of files is what counts in a scan (the results of which are held in a table), and unless you are hashing the files' content, the scan speed is nothing to do with the files' size.
The reason this may affect your performance is that if you have a lot of files and/or low available RAM, the scan-and-compare table may grow so large with a full-scope profile that it impedes performance during the copying stage also (remember that the SAC table is continually updated (think 'juggled') with the results of each action as it is performed, and the final result is then used to generate the logs). If so, using separate profiles might avoid that (SAC table becoming very large / knock-on effects thereof), because each will be (according to your example) ~10% of the size.
The Pro version will switch to a disk-based database long before that could happen, but the Free & SE versions do not (they only use RAM).
Otherwise, I wouldn't expect much difference, but you'd need to try it and see. Bear in mind you'd need to wipe the Destination in-between tests (or use an identical device, or different* base folders on the same device). You should also reboot between tests, to clear any caching of previous file properties by Windows skewing your results
* remember that the second test might hit more fragmentation (have to look harder for available free segments) than the first one (if you use the same device, or if you use separate devices with different capacity and/or free space)
And the number of files is...? Bear in mind the number of files is what counts in a scan (the results of which are held in a table), and unless you are hashing the files' content, the scan speed is nothing to do with the files' size.
The reason this may affect your performance is that if you have a lot of files and/or low available RAM, the scan-and-compare table may grow so large with a full-scope profile that it impedes performance during the copying stage also (remember that the SAC table is continually updated (think 'juggled') with the results of each action as it is performed, and the final result is then used to generate the logs). If so, using separate profiles might avoid that (SAC table becoming very large / knock-on effects thereof), because each will be (according to your example) ~10% of the size.
The Pro version will switch to a disk-based database long before that could happen, but the Free & SE versions do not (they only use RAM).
Otherwise, I wouldn't expect much difference, but you'd need to try it and see. Bear in mind you'd need to wipe the Destination in-between tests (or use an identical device, or different* base folders on the same device). You should also reboot between tests, to clear any caching of previous file properties by Windows skewing your results
* remember that the second test might hit more fragmentation (have to look harder for available free segments) than the first one (if you use the same device, or if you use separate devices with different capacity and/or free space)