June 26, 20197 yr Whenever mover is running in the background, reads from drives that are not involved with mover are very slow ( < 400 KB/s). Specifically, right now I have mover running in the background moving files from the CACHE to DISK1. You can see this in disk activity, DISK1 has reads/writes at ~46.2MB/s matching the PARITY DISK. However when I read something off DISK2 or DISK3, both not in use, reads are globally slow at ~400 KB/s. Any ideas?
June 26, 20197 yr Community Expert This has been an Unraid "feature" for as long as I can remember, any simultaneous array access causes massive slowdowns, you can easily see the same by coping data to one disk and reading from another, both copy operations will slow down a lot, I believe this is related to the md driver and only LT could make some changes to get better performance with simultaneous access, but probably not easy.
June 26, 20197 yr Author I can understand the slowdown due to simultaneous writes because of the parity access, or even a slowdown for simultaneous reads from the same disk drive, but a read slowdown from a drive with no activity is difficult for me to understand. Who is LT, and do you have any reference for how this was done? Thanks.
June 26, 20197 yr Community Expert 6 minutes ago, ensnare said: Who is LT Limetech, the makers of Unraid.
Archived
This topic is now archived and is closed to further replies.