Remember that DSS doesn't provide any RAM cache for BLOCK IO LUNs/shares, only FILE IO, so in that case the SSD cache provided by MaxIQ would be extremely beneficial.Originally Posted by rcohen
Remember that DSS doesn't provide any RAM cache for BLOCK IO LUNs/shares, only FILE IO, so in that case the SSD cache provided by MaxIQ would be extremely beneficial.Originally Posted by rcohen
Sure, if you disable caching on DSS, then you are totally relying on controller caching. Why would you want to do that?Originally Posted by SeanLeyne
All I can imagine is the possibility that the MaxIQ cache algorithm may be better for certain data access patterns. If that is truly happening in real-world applications, it seems like a better solution would be do have some more tunable settings on the DSS cache (size of MRU vs. MFU, etc.)
If the SSD cache provided more bang for the buck than RAM, that would be different, but that doesn't appear to be the case. Apparently, MLC SSDs aren't suitable for caching, due to performance and reliability issues with cache write patterns.
DDS does not do any caching of BLOCK IO LUNs/shares, period. There is nothing to disable.Originally Posted by rcohen
Only File I/O takes advantage of caching by using the extra memory on your motherboard, Block I/O just uses whatever cache you have on your disk controller but none on your motherboad. But you can't do autofailover if your doing File I/O.