bookmarked and b back l8er,i need more info, :-)
bookmarked and b back l8er,i need more info, :-)
Yeah ting, what you said is extreamly true, I tried more time to use our own SSD. But I am helpless on this. Finally I knew through my friend about this.Originally Posted by tingshen
Yeah, its working fine. Thanks for your suggestion....Originally Posted by Robotbeat
Hi mates, thank you very much for all your assistance. All your suggestions are helps me a lot,,,
hey guys, I just recalled I got some posting here lol.
Anyway, we went ahead to get the kit and use it on 5805Z. Unfortunately, under Hyper-V R2, the cache seems a little redundant.....and frankly speaking, it doesn't have any performance benefit for write txn...
I think it will be damn good for web server, those heavy read type.....
For the price of a MaxIQ setup (including SLC SSD), I don't get the benefit of a 32gb SSD cache over 32gb of RAM on the DSS machine.
To me, it seems like the only benefit of an SSD cache is that it persists across reboots. That's nice for a workstation, but it seems useless for a server.
RAM cache is certainly higher performance than SSD.
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.