How many threads does your I/O controller support? Each disk in the array? What about quick disconnects?
As a rule of thumb, two threads per spindle is where I start. But some hardware can support a heck of a lot more than that. And that will overload some hardware. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Leone Sent: Tuesday, January 30, 2018 4:57 PM To: [email protected] Subject: Re: [NTSysADM] Multi-Threading Robocopy On Tue, Jan 30, 2018 at 4:35 PM, Michael B. Smith <[email protected]> wrote: > Doing a /create is going to be MFT lock-bound. You probably won’t get any > improvement above /MT:2. Mostly I put that in there, as preparation for when I run it without the /CREATE this weekend. What I'm really interested in is the thread count when I run a /MIR on a 1.1TB source (I ran the /CREATE based on a suggestion earlier in this thread). > You are probably far more interested in IO Total > than anything else. A single thread can be holding a 64 MB buffer, but > depending on the driver and IO controller there may be darn close to zero > processor usage (and on others it could have a huge impact – it all > depends). > > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Michael Leone > Sent: Tuesday, January 30, 2018 3:16 PM > To: [email protected] > Subject: [NTSysADM] Multi-Threading Robocopy > > > > In my tests, I've been using a thread count of 20 (/MT:20). While doing a > /CREATE only run, it seems to not have any impact on performance (based on > CPU usage in taskmgr). > > > > What's your favorite thread count? LOL > > > >
