![]() ![]() Most people download directly to unraid using docker apps and then share those downloads to thier workstation over smb. ![]() That said if you are doing regular copies larger than your cache consider turning off the cache, using a usb disk, or reducing the mover schedule. You should see a speed improvement for each use case. There is also the issue you found if a copy is too large for one drive it will fail.īy having separate pools you can then assign a physical ssd to the write cache and a physical ssd to your vm. The difference is with one large cache pool if you run your dockers on there and vms too you are really likely to overfill and then crash everything. ![]() 2 drives (parity and drive 1) hitting 30MB/s shows as a total 60. Really though, the amount of cache shouldn't be an issue for me, that was just the original transfer of data into unraid from my Synology.Įdit: just to be clear those speeds I'm seeing are per drive. My cache is a pool of a 500gb drive and a 1tb drive, so perhaps the size difference is causing issues. That was what got me looking into the transfer speeds. I have the minimum free space set at 50GB for that share, but it 100% filled the cache and I had my VMs stop and some dockers freeze up too. It would have to wait for the cache to empty before resuming transfer. My other issue I ran into was copying a bunch of files, the cache filled, and it wouldn't overflow to writing to the array. I have a 500GB cache, so I've just enabled cache for nearly all the shares, and have the mover tuber setup too. The drives I'm using are WD reds, 7200rpm drives. Momentarily hit 31MB/s, that was the fastest I saw. Just tied again then with a 60GB backup file. I get 70mb writes on large files and 40 on small. But mover should be about half your parity check speeds. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |