SATA 3.2 (2000MB/s) would help for throughput but not for latency. It is also still quite uncommon even amongst latest generation servers, whereas this SSD is compatible with many current and older generation servers.
I don't think this SSD can be accessed through regular SCSI, IDE, AHCI controllers. http://www.sandisk.com.br/enterprise/ulltradimm-ssd/
Or flick rapidly between Linux and Windows. That makes me think it might be wise to have a manager to do this. E.g. leave the disks accessible between three+ operating systems.
Isn't that what you already get with suspension to memory (S3)? At least on my Debian laptop, it's ready before the lid is fully up.
- S3 uses battery power (albeit not much)
- NVM provides protection from power faults in datacenters
Of course, if it behaves like a regular SSD, the read speeds still exceed SATA3.0 speed.
Does this mean that for software to take full advantage of this, the software will need to be updated to account for it? For instance, Redis loads data into memory from disk upon starting, but if something like this 400GB SSD is available as memory (and say for instance, 300GB is in use by Redis), wouldn't it make sense for Redis, upon starting, to just "remember" the state of the memory rather than reloading it from disk?
You would not use this to replace RAM, but rather have a second section of memory for persistent data.
I don't think it will work out of the box on regular systems. Also, isn't pcie better for this?