"Remove" transfer speeds slow: 30MBs where 100-180MBs is expected

[APoolTodayKeepsTheNasAway]

Like the post below, it seems that when removing a drive from a pool, transfering is a lot slower than expected. In tests the drive thats having data transferred to it performs as expected with sequential writes (180MBs+) yet here looking at task manager, Im only seeing speeds of up to 50MBS but usually 30MBs with the empty, new, faster drive having the higher utilization percentage.

 

I cant figure out why exactly. Does the remove perhaps try to write multiple files at a time thrashing the drive and causing the low speeds with high usage? I cant imagine thats the case as the drive doesn't sound like its thrashing, yet "remove" always seem this slow, the same speed as balances (even after trying the tweak suggested in the thread below). Id really love to get to the bottom of this as it feels like Im just wasting my time waiting for remove to complete where I could have copied in windows beforehand for a better result. I just cant figure out why this would be slower than that.

[Christopher (Drashna)]

It's using the background priority, for one.  That will reduce the speed at which the moves happen, especially if the disk is in use.

Also, there are a number of other, additional checks that are happening when the drive is being removed, and that may show down the removal process, as well.

Either way, if you don't feel that this is right, open a ticket at https://stablebit.com/Contact.
Enabling logging, and reproduce: http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection
And then run the StableBit Troubleshooter on the system in question: http://wiki.covecube.com/StableBit_Troubleshooter