This is going to be a function of your workload and the class of drive you purchase…
In my server deployments, I have not had a properly-spec’d SSD fail. That’s across many different types of drives, applications and workloads.
Remember, not all SSDs are the same!!
So what does “properly-spec’d” mean?
If your question is about SSD use in enterprise and server applications, quite a bit has changed over the past few years since the original question. Here are a few things to consider:
-
Identify your use-case: There are consumer drives, enterprise drives and even ruggedized industrial application SSDs. Don’t buy a cheap disk meant for desktop use and run a write-intensive database on it.
-
Many form-factors are available: Today’s SSDs can be found in PCIe cards, SATA and SAS 1.8″, 2.5″, 3.5″ and other variants.
-
Use RAID for your servers: You wouldn’t depend on a single mechanical drive in a server situation. Why would you do the same for an SSD?
-
Drive composition: There are DRAM-based SSDs, as well as the MLC, eMLC and SLC flash types. The latter have finite lifetimes, but they’re well-defined by the manufacturer. e.g. you’ll see daily write limits like 5TB/day for 3 years.
-
Drive application matters: Some drives are for general use, while there are others that are read-optimized or write-optimized. DRAM-based drives like the sTec ZeusRAM and DDRDrive won’t wear-out. These are ideal for high-write environments and to front slower disks. MLC drives tend to be larger and optimized for reads. SLC drives have a better lifetime than the MLC drives, but enterprise MLC really appears to be good enough for most scenarios.
-
TRIM doesn’t seem to matter: Hardware RAID controllers still don’t seem to fully support it. And most of the time I use SSDs, it’s going to be on a hardware RAID setup. It isn’t something I’ve worried about in my installations. Maybe I should?
-
Endurance: Over-provisioning is common in server-class SSDs. Sometimes this can be done at the firmware level, or just by partitioning the drive the right way. Wear-leveling algorithms are better across the board as well. Some drives even report lifetime and endurance statistics. For example, some of my HP-branded Sandisk enterprise SSDs show
98% life remainingafter two years of use. -
Prices have fallen considerably: SSDs hit the right price:performance ratio for many applications. When performance is really needed, it’s rare to default to mechanical drives now.
-
Reputations have been solidified: e.g. Intel is safe but not high-performance. OCZ is unreliable. Sandforce-based drives are good. sTec/STEC is extremely-solid and is the OEM for a lot of high-end array drives. Sandisk/Pliant is similar. OWC has great SSD solutions with a superb warranty for low-impact servers and for workstation/laptop deployment.
-
Power-loss protection is important: Look at drives with supercapacitors/supercaps to handle outstanding writes during power events. Some drives boost performance with onboard caches or leverage them to reduce wear. Supercaps ensure that those writes are flushed to stable storage.
-
Hybrid solutions: Hardware RAID controller vendors offer the ability to augment standard disk arrays with SSDs to accelerate reads/writes or serve as intelligent cache. LSI has CacheCade and its Nytro hardware/software offerings. Software and OS-level solutions have also exist to do things like provide local cache on application, database or hypervisor systems. Advanced filesystems like ZFS make very intelligent use of read and write-optimized SSDs; ZFS can be configured to use separate devices for secondary caching and for the intent log, and SSDs are often used in that capacity even for HDD pools.
-
Top-tier flash has arrived: PCIe flash solutions like FusionIO have matured to the point where organizations are comfortable deploying critical applications that rely on the increased performance. Appliance and SAN solutions like RanSan and Violin Memory are still out there as well, with more entrants coming into that space.
