![]() The speed nearly doubled: The time required dropped to 255,7 seconds average with a maximum of 289 seconds and a minimum of 224 seconds. I would expect multi threading to have little to no impact to the speed in this scenario. The average is below 500 seconds (499,8) with a maximum of 612 seconds and a minimum of 450 seconds. ![]() The large single file copies pretty fast (compared to the other files): Multi thread: /DCOPY:DA /COPY:DAT /MT:8 /R:1000000 /W:30) Large Single File The other parameters were left to default (Single thread: /DCOPY:DA /COPY:DAT /R:1000000 /W:30. I copied the scenarios ten times without the multi threading parameter and ten times with /MT. So depending on your network and storage, the result can vary, but the general idea and improvements should apply to your setup too. This tool comes with a lot of parameters, some are more known and some might not be that present to all users.įor this test, I prepared the following scenarios: Most Windows admins should know robocopy, the built-in copy and mirror tool from microsoft. Update: Here is a new article about the impact of more or less threads. I have checked how this parameter impacts the speed of your copy jobs. While some are well known and used, there is maybe the most underrated parameter: /MT for multithreading. Posted on Apby Andy in Windows, Windows Server Robocopy and multithreading: How fast is it?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |