Page 1 of 1

Is it redundant to allocate L2 cache for an SSD drive

Posted: Fri Dec 27, 2019 1:20 am
by LawrenceLee
Support,

I am using Primo cache with a combination of SSD storage drives and a large 4 TB mirror raid drives. I'm noticing when they share tasks with L1 and L2 cache, that the cache apparently is active when I request data from another SSD drive. So it appears that PrimoCache is using SSD space in the L2 cache to cache SSD data. Is this really happening? It seems redundant.

If this is true then it seems that I should the only allocate L1 memory for my SSDs. Should I allocate L1 and L2 cache space for a 4TB spinning hard drive. Or should I rather just use L2 [SSD] cash for my physical hard drive?

Re: Is it redundant to allocate L2 cache for an SSD drive

Posted: Fri Dec 27, 2019 8:11 pm
by cichy45
Yes, Primocache will use L2 SSD cache to cache another SSD if you set your options to do so. Someone might want to cache large 4TB SATA SSD with fast 256GB M.2 NVME for example.


As for your second question - it depends, as always. If you need hundreds of thousands IOPS then you should use L1 RAM cache for your 4TB HDD. If you mainly need sequential performance and lower IOPS (like few thousands per second) then only L2 SSD cache will be enough.
However, if you do not have any heavy load on your disk I would not set cache for SSD at all, only for HDD.

Re: Is it redundant to allocate L2 cache for an SSD drive

Posted: Fri Jan 03, 2020 11:47 am
by Support
You may disable L2 cache for that SSD volume in the "Volume Specifications" in the configuration dialog, if you use a share cache task.