We typically spend a lot of time looking at write endurance when we review enterprise-class SSDs. Write endurance is one of the major differentiators separating enterprise and client-oriented drives, after all. As MLC-based storage continues pushing its way into spaces previously filled by SLC NAND, we have to keep a close eye on this difficult-to-benchmark, but still very important variable involved in evaluating solid-state storage.
The rise of read-focused enterprise drives makes the testing we're doing even more important, since you really want to know what writes will do to storage hardware designed for read-heavy workloads. Naturally, we have to appreciate the companies that treat write endurance as a first-class specification, and much of the credit for that goes to JEDEC for its JESD218A write endurance testing standard. Instead of issuing vague ratings, we now see most companies specifying their drives to JESD218A, which uses the JESD219A enterprise workload to quantify endurance. This closely matches the types of workloads we use in our Enterprise Workload Performance tests, employing sequential write patterns and large block sizes. The result is minimal write amplification and wear leveling, yielding a better indication of actual P/E cycles for the NAND.
| Endurance Rating Sequential Workload, QD=1, 8 MB | Intel SSD DC S3500 | Seagate 600 Pro | Intel SSD DC S3700 |
|---|---|---|---|
| NAND Type | Intel 20 nm MLC | Toshiba 19 nm MLC | Intel 25 nm HET-MLC |
| RAW NAND Capacity | 528 GB | 256 GB | 264 GB |
| IDEMA Capacity (User Accessible) | 480 GB | 200 GB | 200 GB |
| Over-Provisioning | 9% | 28% | 32% |
| P/E Cycles Observed (IDEMA) | 3,326 | 6,245 | 36,343 |
| P/E Cycles Observed (RAW) | 3,024 | 4,879 | 27,532 |
| Host Writes per 1% of MWI | 15.97 TB | 12.49 TB | 72.69 TB |
| $/PB-Written | $362.55 | $228.18 | $64.66 |
As we saw in Seagate 600 Pro-Series 200 GB SSD Review: For The Enterprise, read-focused SSDs are ill suited for write-intensive applications. Compared to the SSD DC S3700, you get roughly one-tenth of the endurance for half of the price. We don't consider that a good deal. Fortunately, you don't buy this drive for its great write endurance. You simply want to know what it'd do if you were to tax it with writes.
The bad news is that, up against Seagate's 600 Pro, write endurance looks even worse for the SSD DC S3500. Seagate's drive holds a commanding 60% lead in P/E cycles observed.
Now, we'll step back and consider what the two companies say about endurance. They both present specifications using the JESD218A standard, and they both sell 480 GB SSD. Intel states its write endurance at 275 terabytes written (TBW), while Seagate states 350 TBW. That's not the 60% we observed, but it's still a large 27% difference.
It's more difficult to compare write endurance between capacities. With Intel, the odd NAND configurations change over-provisioning at each capacity point. This means that the 800 GB model has exactly twice the endurance rating as the 400 GB version, but the 480 GB drive is slightly less than double that of the 240 GB SSD. Seagate, meanwhile, uses a complex endurance rating system based on the amount of factory over-provisioning. The 200 GB 600 Pro that we tested is rated at 520 TBW, while the 240 GB version, with the exact same amount of NAND, is rated at only 134 TBW. Even this ratio of TBW varies across capacities, from 3x to nearly 10x.
What does all of this information tell us about write endurance? Like all tests that involve random, small-block workloads (JESD218A), write endurance is heavily affected by over-provisioning. This is one of the reasons we test with large-block sequential workloads. The low write amplification helps us see through any configuration FUD. We weren't able to put that theory to the test by over-provisioning the SSD DC S3500 to 600 Pro levels in this story, but expect that analysis in the near future.
Bringing it all back to Intel's SSD DC S3500, by all measurable and stated results, Seagate's 600 Pro provides higher write endurance. With that in mind, how important is write endurance on a drive that was not made for write-intensive applications? Now more than ever, this SSD encourages you to be educated about the workloads you apply to it, else you spend a lot of time and money on replacements.
- Intel SSD DC S3500: Focusing On Read Performance
- Inside Intel's SSD DC S3500
- Test Setup, Benchmarks, And Methodology
- Results: Write Endurance
- Results: 4 KB Random Performance And Latency
- Results: Performance Consistency
- Results: Enterprise Workload Performance
- Results: Sequential Performance
- Results: Enterprise Video Streaming Performance
- SSD DC S3500: Not Quite An S3700 Or 600 Pro
''...we do know that the 800 GB model we're reviewing should run around $579. At ~$1.20/GB, ...''
800GB @ $1.20 = $960.
''...we do know that the 800 GB model we're reviewing should run around $579. At ~$1.20/GB, ...''
800GB @ $1.20 = $960.
Thanks, just can't seem to get the right combination of 4, 8 and 0. The 480GB version is $579
With the BAD_CTX_13X (8MB) failure, the fixed firmware fixed 'most' of them. The failure rates are quite low, especially after the FW 'fix', but if that one failure happens on the only drive you bought, it can really suck. As a consumer, I could care less if a million other people got a good SSD, if mine fails, I am upset. As an enterprise buyer, if one fails out a million, my company is throwing a party!
With the BAD_CTX_13X (8MB) failure, the fixed firmware fixed 'most' of them. The failure rates are quite low, especially after the FW 'fix', but if that one failure happens on the only drive you bought, it can really suck. As a consumer, I could care less if a million other people got a good SSD, if mine fails, I am upset. As an enterprise buyer, if one fails out a million, my company is throwing a party!
I'm sorry Drew, but that's flat out wrong.
BAD_CTX_00000013X is lierally just a single error code that is related to the 8MB bricking issues of the 320.
Intel didn't fix "most" of anything. There are many other instances of the BAD_CTX and NO_CONTEXT errors.
Intel literally fixed only the most common version of the BAD_CTX bug and did NOTHING about the underlying issue plagueing the 320.
Frankly, there's not much more they could have done than because the 320 was a bad design based on porting the X-25 controller and slapping on 32nm memory that it wasn't robust enough to handle.
It looks like Intel has done the same thing here by slapping 20nm NAND onto the 3700 and renaming it.
Maybe they think adding "Data Center" to it's name will somehow cause it to brick less?
Anyway, continuing to endorse the 320 as a reliable drive is just bad journalism. It's certainly not the worst out there, but the 320 is still significantly over-represented in failure rates vs micron/crucial and samsung.
Go back and read the article.
Or, learn the difference between consumer vs commercial. It's a DT (Data Center).
Go back and read the article.
Or, learn the difference between consumer vs commercial. It's a DT (Data Center).
Fair enough, I guess I should have been more clear. I don't understand why Intel is involved with so many mediocre SSDs - whether enterprise or consumer.
While I am not an enterprise user, I think I understand the basics. Enterprise SSDs are geared to handle heavy cues and write loads.
You have a point that it is not fair to compare enterprise with consumer - they are two different animals.
It would be really helpful to have a review focused on answering the question of which SSD is most suitable for a Windows 7 boot drive.