- Joined
- Oct 20, 2019
Not sure. It does have some settings you can tweak. Let me try changing them around and also seeing if I can spot a different number of cores or threads used between FastCopy on a couple of different settings and also against raw Windows copy in Resource Monitor.I take it this would mean that the problem is to do with Windows Copy itself and not NTFS then? I have heard one theory being that WC is single threaded causing the slow performance but I don't know, what do you think?
A few minutes later...
So File Explorer is not single-threaded in its file copy. It varied between 4 and 8 CPU cores (logical) whilst copying a project folder.
FastCopy sat consistently on 4 cores during its run.
FastCopy does have some things disabled by default, like "Verify". I enabled that to see what difference it made just as an example. Increased the time from 16 seconds to 22.
Their website does say its speed is "because it uses multi-threads for Read/Write/Verify, Overlapped I/O, Direct I/O", so my rudimentary quick test isn't showing whatever magic they're doing to achieve this.