This means a total of 270 copy jobs.įor each run I logged the duration using the column “Copied” and “Extras” plus the sum of both.Why did you choose to copy via the desktop deviation instead of copying directly?īecause our company have like 75 desktop i cant put all of them in the switch of the NAS I started each scenario with the following thread count: No MT, 1, 2, 4, 8, 16, 32, 64, 128.

For runs with “No MT” I completely omitted this parameter. NFL means that the files transferred will not be listed. I checked after each run if all files have been transferred without issue. W and /R means that robocopy retries reading/writing files only once. Robocopy.exe sourcepath destinationpath *.* /W:1 /R:1 /NFL /MT:n I used the following command to copy the files to the NAS: Similar to the old test, I have prepared 3 scenarios with a volume of ~20GB each: So you cannot compare the results from the earlier test with this test (And you will see that there are a lot of differences). So the transfer rates might be higher or lower in your environment and some runs might be impacted by processes or users using the system.Īlso please note that this is based on an entirely new setup. It’s my daily computer and an active NAS. The files are being transferred to a NAS over an ethernet connection.

This gives me 4 cores with 8 logical processors. The setupįor this test I am using a notebook with an Intel Core i7-8550U cpu. This leaves us to question: How many threads do we need? And means more threads = more power? Let’s find out. In my previous test I have shown that copying/transferring files with /MT is in general faster than not using the parameter. But does more threads mean faster transfers? Robocopy allows you to transfer files with multiple threads.

Copy files faster windows 10