Microsoft suggests that multi-threaded Robocopy helps with network throughput as well. I repeated the first single-threaded test again and watched it dawdle along, taking over a minute again to finish. Using “/MT:32” was blazing fast – easily less than 15 seconds. Copying my entire “Program Files” directory took well over a minute without multi-threading, but simply specifying “/MT” at the end of the command reduced a second copy to a different directory to about 20 seconds. I tried out the new /MT option on a Core 2 Duo laptop and was surprised by the dramatic improvement in copy performance. However neither this nor /IPG (inter-packet gap) can be combined with the multi-threaded option mentioned above.
This defaults to 8 threads, but users can specify up to 128 if desired.
It was single-threaded, hurting performance on high-latency networks, and startup was painfully slow on deep directory structures. It also tolerates dropped connections, resuming where it left off, and can throttle operations over slow networks.īut Robocopy was never very quick, especially when dealing with large data sets. It’s the best tool to move data between NTFS filesystems, since Robocopy maintains permissions and file attributes. It's hard to take a product called "Robocopy" seriously!Īnyone doing much storage work on Microsoft Windows machines is familiar with Robocopy.
0 kommentar(er)
