Hello everyone. Recently came back to using unRAID after stepping away for a few years. Came back specifically to make use of the new features in version 6+. I am running an i7 systems with 32GB memory, GTX960 to pass through to the VM, 3x 3TB drives for the array and 3x 240GB SSD for the cache.

 

That said, I am having what I believe is an issue with the access speeds between the Windows 10 VM and the disk array. I can start transferring files between the two, and it bursts out at 550MB/s, but drops to 35-40MB/s after 2-3 seconds. I am not expecting to get 500+MB/s out of the spindles in the array by any means. I was expecting to get 120+MB/s out of them however. Is this unreasonable, or does there appear to be an issue here to be worked out?

 

Cheers

Are you reading or writing?    If writing are the shares in question set to use the cache drive? 

 

30-40MBps is not untypical if writing to shares that are not set to use the cache.  For reading (or writing to shares that use the cache) then speeds more like 100+MBps is more typical.

Writing direct, skipping the cache. Reading isn't quite as bad. Looking around it does look like this is pretty typical. Was thrown off as these same drives were seeing double that transfer when they were part of a windows machine. If this is the case, I will work with it and look at upping the cache pool as well.

 

Thanks.

Writing direct, skipping the cache. Reading isn't quite as bad. Looking around it does look like this is pretty typical. Was thrown off as these same drives were seeing double that transfer when they were part of a windows machine. If this is the case, I will work with it and look at upping the cache pool as well.

Writing direct to the array will always be relatively slow as each write involves 2 reads (data disk and parity disk) followed by 2 write (data disk and parity disk).  This is required if unRAID is not to spin up all the disks when writing.