bobloadmire

hmm i'm set to balance daily at 3am. my ssd cache is constantly sitting full, advice?

I bought an ssd to use as cache, so it could fill it, and then once a day dump the cache to the archive drives, rinse repeat. but now that the archive drive has filled up, I hear constant clicking from writes to the drives 24/7. Is there anyway to setup a scheduled dump of the cache to the archive drives so they can idle for the vast majority of the day?

thank you, clear and concise. Re #1, seems like it shouldn't be too hard to implement, would be very powerful feature.

2 questions. 1. Can I specify to keep the most recent files in the SSD cache for faster reads, while also duplicating them to archive disks during the nightly schedule? Essentially files would be duplicated at night during down time, and also files wouldn't be deleted from the SSD cache. However the cache would operate on a first in/last out algorithm, so that the most recent files would be kept on the cache for faster access? once the oldest file is to be replaced by the newest file, it would just get deleted from the cache since it would have been placed on the archive disk. 2. can I specify some folders to always be on the SSD cache? for instance my Plex database would be great to have permanently in the SSD cache. I have no need to duplicate this database, as it can always be rebuilt easily. Thanks!

unfortunately, didn't make a difference, still limited to about 700mbps

It would be great to allocate some dis space (say 10TB/disk or something) that would be a dedicated folder or even drive letter for striped writes. This would be great for usenet/torrent downloads, or when your bandwidth exceeds a single disk performance, or when unpacking PAR files. That way I could unpack directly in the stripped pool space and then just move the files to the standard pool space. Or another option would be to make all writes striped and then have the duplication / movement of files to a single disk happen in the background so you could have immediate access to the files with the advantage of having them unpacked faster.

Ok did that, CMD output "OK" so I assume that did it. still capping out at 730ish mbps. Do I need to run that on the client machine as well?

Would there be any benefit to duplicating game data so you can do striped reads? optimal amount of duplications?

basically an optimization question. I tested all 4 of the disks in my pool with Scanner, they all did about 250-350MB/s, so my USB controllers are good. I enable jumboframes on both the host and clients. Internal SSD has fantastic performance 600MB/s to the buffers and sustains 250-300MB/s after that. I have network i/o boost on, but I cannot get more than about 600Mb/s over the gigabit network, and I'm expecting to get 900+ with overhead. Any tips at things I should look at?