The Intel Optane Memory (SSD) Preview: 32GB of Kaby Lake Caching
anandtech.com
anandtech.com
What I had in mind wasn't that these would be replacements for existing solutions used for high sustained intensity applications directly making money. Those are covered by ram drives or striped SLC already (and perhaps the P4800X series soon). I was more thinking the Optane Memory might provide a solid route for experimentation by a new class of users given the capex of a few pizzas. A lot those cases are going to be relatively low sustained intensity, but with burst performance still desirable. Heck, for forty someodd bucks some might go for it just to do some profiling and get a feel for what a separate ZIL would do for them at all.
If anything a significant limiting factor right now may simply be the relative availability/preciousness of M.2 slots in deployed home/soho appliances, servers and workstations.
It's unfortunate that it's only available for Kaby Lake, since I imagine that most people in need of a HDD cache run much older systems.
I get to experience lovely things like performance falling off a cliff when stupid programs preallocate 30-40 gigs at a time. If I could use the rest of the SSD it would be no problem.
What desktop user needs fast write caching for synchronous writes? I mean really. It's all buffered writes for programs that work right. Cache size is going to give power desktop users what they need from spinning rust not a small fast cache that won't even fit a single AAA game. 32 gigabytes is a step backwards.
And what is with requiring hardware RAID? It really makes me think all the rapid response stuff is just for marketing.
Intel doesn't really do hardware RAID, just software RAID that the motherboard firmware has a compatible implementation of for boot purposes. There is one hardware feature that Intel relies on for RAID or caching involving NVMe drives: the PCH can remap the PCI registers of NVMe drives so that the NVMe drive is only accessible through non-standard interfaces on the SATA controller. This prevents non-Intel NVMe drivers from binding to the NVMe drive and getting in the way of their caching or RAID. It's a hardware hack Intel created to work around poor software architecture.
Queue depth is being hyped but means basically nothing for commercial SSD's that have battery backed ram cache. The SSD just queues writes until queue depth is deep enough.
Extraordinarily few SSDs, even commercial, have battery backed caches (and those that do often turn into a reliability nightmare), and when they do it tends to be relatively tiny compared to the scope. Queue depth is profoundly important in the real world.
You can get 120GB of SSD for that price, and it would probably do a better job as a hard drive cache.
But yes the better performance at doing persistent writes is very useful for some cases.
I was wondering if this will be any helpful for a product I am working on, but as I use mmap for reading our data, don't really see a benefit after the initial read.
Or your filesystem caching often requested disk blocks which had to be removed because of memory pressure.
Since write endurance is spread over the whole SSD you can easily get a cache four as big as the Optane equivalent for I presume the same amount of money and end up with the same endurance, higher throughput, slightly more latency, and a much higher cache hit rate.
So, no, if you have 1TB of memory a 32GB Optane SSD isn't going to make a difference, but if you have 1TB of memory, you're not the target for the 32GB consumer version, you're the target for the 375GB+ datacenter version.
[1]: http://www.anandtech.com/show/11209/intel-optane-ssd-dc-p480...
Keeping in mind that that version costs $4/GB, which is about half the price of adding more RAM. Which means that while it can be good storage for ZFS or a database, it's still not a particularly effective cache in such a machine.
but still what I wanted to say is that it is prolly more useful as a ssd read cache. and not to have it behind your big memory.
The other thing I don't get is that Intel wants to sell Optane drives to "eSports gamers". Why would they need that? I've heard people on the Overwatch forums complaining about slow map loading from laptop hard drives... but if you're playing organized eSports, they're not going to start the match without you. Matches are paused mid-match all the time for technical glitches. If you're just playing on your machine at home, that's not really eSports, that's just playing computer games at home, perhaps with a higher than average dedication to winning. And map loading time is miniscule with SSDs, so I don't see the advantage you could possibly derive from there. (It all fits in RAM anyway, which is cheap.)
I dunno, I kind of see this whole thing as a solution without a problem, at least in the consumer market.
Intel knows that Optane caching isn't an attractive high-end solution; they're not trying to pitch it against the 2TB Samsung 960 PRO. They'll be coming out with higher capacity Optane SSDs for primary storage use later this year, though still sacrificing a lot of capacity for the improved performance relative to NAND flash.
Maybe the next generation of Optane will be worth it, but this generation certainly is not.