Slashdot Mirror
Intel Launches SSD 750 Series Consumer NVMe PCI Express SSD At Under $1 Per GiB
MojoKid writes Today, Intel took the wraps off new NVMe PCI Express Solid State Drives, which are the first products with these high speed interfaces, that the company has launched specifically for the enthusiast computing and workstation market. Historically, Intel's PCI Express-based offerings, like the SSD DC P3700 Series, have been targeted for datacenter or enterprise applications, with price tags to match. However, the Intel SSD 750 Series PCI Express SSD, though based on the same custom NVMe controller technology as the company's expensive P3700 drive, will drop in at less than a dollar per GiB, while offering performance almost on par with its enterprise-class sibling. Available in 400GB and 1.2TB capacities, the Intel SSD 750 is able to hit peak read and write bandwidth numbers of 2.4GB/sec and 1.2GB/sec, respectively. In the benchmarks, it takes many of the top PCIe SSD cards to task easily and at $389 for a 400GB model, you won't have to sell an organ to afford one.
From what I've seen, the standard reaction of SSD firmware when write integritiy can't be guaranteed is "commit suicide".
That was true of some of the OCZ Vertex series and other make/models. But this last generation of SSDs seemed to have made that a rarity even under the most extreme conditions.
In the case of this new Intel PCIe SSD card, I believe it has enough capacitance to commit a complete transistor write upon system power failure. As for the lost data for non-commited data?? Well, you're are running a journaling file system, yes? At least the volume won't get corrupted. But anyways yeah, seems like a solid drive you can rely on. Time will tell of course.
Life is not for the lazy.
It's called backups. They're cheap an easy and entirely your responsibility. A USB 3.0 hard drive + automated daemon or a 30 dollar/yr cloud based service.
Predictable, documented failure modes are preferable to silent data corruption. A device predictably scuttling itself when data state becomes inconsistent is proper, desirable behavior.
Your lack of backups are a different problem.