SSD Optimizer Question

[Angryunibrow]

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!

 

 

 

 

 

[Christopher (Drashna)]

Yes, basically.

 

However, if you're using the SSD Optimizer balancer plugin, and you're using duplication, that you'll need two SSDs for the SSD Optimizer, or duplicated data will be written to a mechanical drive as well, slowing down the speed. 

 

BitTorrent shouldn't have any issues with the pool.  I store torrents on a "temp" pool, without any issues.  The caveat is that if the torrent is active, then it won't get moved off of the SSD, as we can't move open files to a new disk.  You'd need to stop it from seeding, let it balance off of the drive and then re-seed. 

[Angryunibrow]

Perfect, Thanks for the reply

 

I will not be using any duplication so i'm covered there.

[Angryunibrow]

Edit: Never-mind, figured it out

[Christopher (Drashna)]

Yeah, if you're not using duplication, then a single SSD for the pool is perfectly fine.  

 

 

As for the other, (edited) content, the balancing settings influence that. I would recommend a higher threshold for the SSD, as once the SSD is filled to this threshold, it will place files on "archive" disks.  

 

But setting the balancing ratio (in the "Settings" tab) to 100% will make it more aggressively balance the data off of the SSD. As will setting it to "balance immediately" and unchecking the "but not more often than" option. 

 

And when adding files, it's written to the SSD first, but in the pool folder structure, so it shows up on the pool. Then the balancing engine will move it to another disk, and it will appear in the pool and in the "correct" location the entire time. 

[Angryunibrow]

Yeah, if you're not using duplication, then a single SSD for the pool is perfectly fine.  

 

 

As for the other, (edited) content, the balancing settings influence that. I would recommend a higher threshold for the SSD, as once the SSD is filled to this threshold, it will place files on "archive" disks.  

 

But setting the balancing ratio (in the "Settings" tab) to 100% will make it more aggressively balance the data off of the SSD. As will setting it to "balance immediately" and unchecking the "but not more often than" option. 

 

And when adding files, it's written to the SSD first, but in the pool folder structure, so it shows up on the pool. Then the balancing engine will move it to another disk, and it will appear in the pool and in the "correct" location the entire time. 

 

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!

[Christopher (Drashna)]

Yup, exactly.  

 

And again, just keep in mind that the SSD limit is for how full it can get until it starts placing files onto other drives. So 75% or higher is a much better option.