Angryunibrow

Yeah, after I wrote that post it made more sense to me. I keep forgetting the SSD is still actively part of the pool and the files will be placed on that first, then balanced out at a later time. They will always show up on your pooled drive letter (in my case I:) instantly. Thanks for the help!

Edit: Never-mind, figured it out

Perfect, Thanks for the reply I will not be using any duplication so i'm covered there.

Hello Everyone I have installed the trial version of Drivepool on an old system (with no SSD unfortunately) just to test things out. Because I do not have access to an SSD it was hard for me to test this out, to see the increased speeds. If I understand this correctly this is what I would like to happen, and I believe this is what does happen. My new server will consist of a Samsung 950 pro M.2 512 SSD for the OS drive and used as the main drive. (This will NOT be included in the pool) This will be my C:\ In front of my hard drive storage i will place another Samsung 950 pro M.2 512 SSD to act as the SSD optimizer. So in theory this should copy from my C: drive to the 2nd 950 pro (Cache Drive) at incredibly speeds and then balance the data out over the mechanical hard drives. Correct? I will be dealing with very large files at times, in excess of 30-40GB a piece. (Blu-ray rips) and I want the best performance i could possibly get while moving files around. While I'm here I have 1 more question How does bittorrent act while torrenting to the pool? Will I be able to torrent directly to the pool and continue to seed with no issues? And will this torrent to the SSD Cache drive first, and then distribute the file once it is complete, if so how does that effect seeding? Thanks!