Flash Myths, Tested

Do SSDs Wear Out in a Couple of Years?

My SMART data from a system drive, a test bench, new and used drives, against the ratings and field studies: a desktop SSD wears far slower than the myth says.

On this page 8 sections

This is one of the myths in Flash Myths, Tested, where each common belief about SSDs gets checked against data, specs and papers. The belief here is that SSDs wear out in a couple of years, and the question is how fast a desktop drive really uses up its life.

Do SSDs wear out in a couple of years: what a desktop writes, what new drives show, what two years would takeA three-panel schematic. Left: my 4TB system drive writes about 96GB a day and reports 1% used. Center: 70 of 83 new drives read 0% or 1% used at the end of a test suite. Right: reaching a 600TBW rating in two years takes 822GB of writes a day.FLASH MYTHS, TESTED / ENDURANCETwo years takes far more writesMY DRIVE · NEW DRIVES · THE RATING01 MY DRIVE96GBwritten a dayBar scaled topanel 0302 NEW DRIVES70 of 83at 0% or 1% usedAfter a fulltest suite03 THE RATING822GBa day to use up600TBW in two yearsArithmetic, not ameasurement

My 4TB NVMe system drive has run for 10,726 power-on hours and written 42.9TB, about 96GB a day, and it reports 1% of its life used. Using up the ratings I checked in two years would take 275GB to 5,479GB of writes every day, so for desktop use the myth doesn’t hold.

Where the myth comes from

The worry rests on a true fact. Flash cells wear out as they are programmed and erased, and every drive carries a limit. In the Google fleet study the MLC drives had a limit of 3,000 program/erase cycles, and a number that small sounds like it could run out in a couple of years. Flash Foundations Part 9 explains how makers turn that limit into the TBW rating on the box.

Where the myth comes from

The limit is real, but the myth skips how fast real use reaches it

From a cell’s cycle limit to the rating and the number the drive reports

Four stacked boxes joined by arrows pointing down. One, the cell: every program and erase cycle wears a flash cell, and every drive carries a limit on those cycles. Two, the rating: the maker turns that limit into the TBW rating on the box. Three, the estimate: the drive reports its own estimate of wear used, Percentage Used. Four, drawn dashed because it is missing from the myth: how many cycles real use takes.01 THE CELLEvery program and erase cycle wears a flash cell.Every drive carries a limit on those cycles.02 THE RATINGThe maker turns that limit into the TBW rating on the box.03 THE ESTIMATEThe drive reports its own estimate of wear used:Percentage Used.04 WHAT THE MYTH LEAVES OUTHow many cycles real use takes.What the myth gets rightWhat the myth leaves out
A cell’s cycle limit becomes a rating and a reported estimate, and the myth leaves out how many cycles real use takes. Source: Schroeder and colleagues (Google fleet study), Flash Foundations Part 9, NVMe specifications.

The myth leaves out how many cycles real use takes. Below, my own SMART logs come first, then the ratings, then the field studies, and one caution runs through all of it. My data comes from desktop and bench use, and the field studies come from data centers.

What my own drives show

My system drive is a 4TB NVMe SSD that I use every day, and a read-only smartctl capture of its SMART log shows 83,853,719 data units written. A data unit is 512,000 bytes, so that is 42.9TB of host writes, about 10.7 times the drive’s capacity, over 10,726 power-on hours, which is 447 days. That works out to about 96GB a day across everything on the drive, and it reports a Percentage Used of 1%.

Percentage Used is the drive’s own estimate of how much of its endurance is gone. It’s a whole number, 100 means the estimated endurance is consumed, and the value can go above 100. Kingston’s Fury Renegade data sheet ties its warranty to that number: five years or a Percentage Used of 100. So the vendor’s estimate is the number that matters for a warranty claim, and mine reads 1%.

This is one machine, and 447 days isn’t two years. It gives me a rate, and the myth needs to be tested against a rate.

A second set of captures comes from a drive that held the operating system on my test bench. I read its SMART log 126 times across 1,229 power-on hours. Over that time its host writes rose from 17.55TB to 22.19TB, an increase of 4.64TB, about 91GB per 24 hours of power-on time. Its Percentage Used read 1% at every capture.

What my own drives show

Writes climbed steadily while Percentage Used stayed at 1%

SMART log of the drive that held the OS on my test bench, 126 captures

A line chart of terabytes written against power-on hours. Across 126 captures, over 1,229 power-on hours, the line rises from 17.55TB to 22.19TB, an increase of 4.64TB. The drive's Percentage Used read 1% at every capture.Host writes, TB16182022243006009001,2001,500Power-on hours17.55TB22.19TBTB written at each captureFirst and last capture
Figure 1 · The drive went from 17.55TB to 22.19TB written over 1,229 power-on hours, and read 1% used every time. Source: Sean Webster’s own SMART captures, brand withheld.

Figure 1 draws all 126 captures. The climb is steady and gentle, and the wear estimate never moved. I withhold the brands. Figure 1 shows the OS drive with the most captures, out of the four the bench went through.

What new drives show

New drives make up the third set, and when I review one I read its SMART log at the end of the test suite. For 83 new NAND drives, the median total was 16.45TB written, reached in a median of 42 power-on hours, and the range ran from 1.87TB to 57.77TB. I left out the two Optane drives and two records with no usable write count.

What new drives show

Most new drives finish a test suite at 0% or 1% used

83 new NAND drives, binned by TB written at the end of the suite

A bar chart of 83 new NAND drives by terabytes written at the end of a test suite, in equal bins. 8 drives in the bin starting at 0, 13 drives in the bin starting at 5, 16 drives in the bin starting at 10, 22 drives in the bin starting at 15, 4 drives in the bin starting at 20, 11 drives in the bin starting at 25, 4 drives in the bin starting at 30, 2 drives in the bin starting at 35, 2 drives in the bin starting at 40, 1 drives in the bin starting at 55. The median is 16.45TB. A dashed line marks my system drive at 42.9TB written after 10,726 power-on hours.Number of drives0510152025801351610221542011254302352404550155TB written at the end of the suite (each bin labeled by its start)My system drive42.9TBNew drives in each binMy system drive, total
Figure 2 · The median drive had 16.45TB written; 70 of the 83 read 0% or 1% used and the highest read 6%. Source: Sean Webster’s own SMART captures, brand withheld.

Figure 2 bins them. Of the 83 drives, 70 read a Percentage Used of 0% or 1% and the highest read 6%. This shows how hard a test suite writes, not wear over time, because every drive was new when I started. A median suite total of 16.45TB is what my system drive writes in about 171 days.

The drives that read more than 1% are a reminder that Percentage Used is measured against each drive’s own rating, and the ratings of these drives aren’t in my archive, so I can’t say what share of its rating each drive spent. I can say that none of them was close to 100.

What two used drives show

A fourth set comes from a second set of drives from my work bench. It gives me two used drives, both 2TB. I read them with CrystalDiskInfo, so the health figure here is the Health Status percentage that CrystalDiskInfo prints. It isn’t the NVMe Percentage Used counter that the other sets report, and I keep this set apart from them instead of pooling the numbers.

The first drive was read 48 times across 145 to 2,973 power-on hours, and its host writes rose from 7.2TB to 14.3TB, a rise of 7.0TB that averages about 60GB per 24 hours of power-on time. That average hides how it happened, because the writes arrived in steps between sessions on the bench. CrystalDiskInfo health read 100% until the capture at 2,920 power-on hours and 14.2TB written, and 99% at the last 4 captures.

What two used drives show

Writes arrived in steps, and health slipped from 100% to 99%

CrystalDiskInfo readings of one used 2TB drive, 48 captures

A line chart of terabytes written against power-on hours. Across 48 captures the line rises in steps from 7.2TB to 14.3TB. CrystalDiskInfo health read 100% at first and 99% at the last 4 captures.Host writes, TB681012141607501,5002,2503,000Power-on hoursHealth 99%from here7.2TB14.3TBTB writtenFirst, last captureFirst 99% health
Figure 3 · Host writes went from 7.2TB to 14.3TB over 2,828 power-on hours. CrystalDiskInfo health read 100% at first and 99% at the last 4 captures. That is not the NVMe Percentage Used counter. Source: Sean Webster’s own CrystalDiskInfo captures, brand withheld.

A second drive was read 17 times across 248 to 582 power-on hours. It had 45.7TB written at the first capture and 48.1TB at the last, more than the 42.9TB on my system drive, and CrystalDiskInfo health read 97% at every capture.

This set is thin. It’s two drives. Neither drive’s rated TBW is in my data, and health isn’t Percentage Used, so I can’t say what share of its rating either drive spent. It adds one plain observation. A drive with 48.1TB of host writes still read 97% healthy, and a drive with 14.3TB read 99%. That fits the verdict, but two drives can’t prove it.

What wearing out in two years would take

Take two years as 730 days. A rating is a total, so the daily write that reaches it in two years is the rating divided by 730. TBW is worked out from the flash’s program/erase budget, the drive’s spare area and an assumed write amplification, so you compare it directly with the host writes in SMART, as Part 9 describes.

What wearing out in two years would take

Using up a rating in two years takes far more than I write

GB written a day: what I measured, and what reaches each rating in 730 days

A horizontal bar chart of gigabytes written a day, from 0 to 6,000. My system drive: 96GB a day, measured. 512GB rated 110GB a day: 275GB a day, needed to reach the rating in two years. 1TB rated 600TBW: 822GB a day, needed to reach the rating in two years. 4TB rated 4.0PB: 5,479GB a day, needed to reach the rating in two years.Drive and rating01,5003,0004,5006,000GB written a dayMy system drivemeasured96512GB rated 110GB a dayfor five years2751TB rated 600TBWSamsung 870 EVO8224TB rated 4.0PBKingston Fury Renegade5,479Measured on my driveNeeded to reach the rating in two years
Figure 4 · My system drive writes about 96GB a day; reaching the 1TB drive’s 600TBW in two years takes 822GB a day. Source: Saved datasheets (Samsung 950 PRO, 870 EVO, Kingston Fury Renegade); my SMART capture; arithmetic by Sean Webster.

Figure 4 sets my measured 96GB a day beside three ratings from saved data sheets. Samsung rated the 512GB 950 PRO at 110GB a day for five years, which is about 200TB in total, and two years reaches that at 275GB a day. Samsung rates the 1TB 870 EVO at 600TBW, which is 822GB a day. Kingston rates the 4TB Fury Renegade at 4.0PB, which is 5,479GB a day. I don’t have a saved rating for my own drive, so the three ratings belong to other drives.

Ratings aren’t arbitrary. Kingston says its TBW is derived from the JEDEC client workload, JESD219A, and the SNIA endurance white paper says vendors rate TBW with the JESD219 trace for the drive’s class. SNIA also notes that most consumer use is write once, read many, and that only heavy content creators and power users regularly move tens to hundreds of GB.

What the field studies add

The two big field studies are data-center fleets, which usually write far more than a desktop, so they make a conservative case. Schroeder and colleagues studied drives in Google’s fleet for up to six years. MLC models had averaged 529 to 949 program/erase cycles against a limit of 3,000. The eMLC models averaged 377 to 607 against 10,000, and the SLC models 185 to 860 against 100,000.

What the field studies add

Fleet drives averaged fewer cycles than their limits

Google fleet models, average cycles used against each class’s limit

A horizontal range chart on a logarithmic axis of average program/erase cycles, from 100 to 100,000. MLC models: averaged 529 to 949 cycles against a limit of 3,000. eMLC models: averaged 377 to 607 cycles against a limit of 10,000. SLC models: averaged 185 to 860 cycles against a limit of 100,000.Drive class1001,00010,000100,000Program/erase cycles, log scaleMLC models529 to 949limit 3,000eMLC models377 to 607limit 10,000SLC models185 to 860limit 100,000Range of average cycles usedCycle limit
The MLC models averaged 529 to 949 cycles against a limit of 3,000, the eMLC 377 to 607 against 10,000 and the SLC 185 to 860 against 100,000. Source: Schroeder and colleagues, Google fleet study, up to six years.

Errors grew linearly with cycles, with no sudden spike past the limit in the range they studied, and age mattered on its own. The vendors’ accelerated tests showed a rapid rise only at about 3 times the limit, which led the authors to call the limits conservative. Meza and colleagues, studying Facebook’s fleet, found 14.8TB to 48.5TB written to flash per SSD over average ages of 0.5 to 2.4 years. They also found that failures do not rise steadily with wear, and that the data the operating system writes does not always match the wear on the flash, because of controller optimizations and buffering. That second point is why I read the Percentage Used field as well as the writes.

Where the myth could be true

A couple of years is plausible for one case. Those numbers show it. At 275GB a day, the 512GB drive in Figure 4 would reach its rating in two years, and that is inside the range SNIA calls heavy creators and power users. A small drive under a heavy creative workload can wear out that fast.

Where the myth could be true

A small rating under heavy writes can be used up in two years

Share of a rating that two years of writing uses, by case (proportions illustrative)

Two panels, each with a bar for a drive's rating, the total writes it allows. In the first, a small rating under heavy writes, the bar is filled completely: the rating is reached in about two years. In the second, a large rating under light writes, only a small part of the bar is filled. Below the panels, the arithmetic: days to reach the rating equal the rating divided by the writes per day. A note says what is not measured: drives with the lowest ratings and a creator's workload.01 HEAVY WRITESSmall drive, creative workloadRating, the total writes allowedShare used by two years of writingThe rating is reachedin about two years02 LIGHT WRITESLarge drive, desktop useRating, the total writes allowedShare used by two years of writingA small share of therating is spentDays to the rating = the rating ÷ the writes per dayNot measured: drives with the lowest ratings,and a creator’s workloadRating, the total allowedShare used in two years
The rating is a total, so heavy daily writes against a small rating can reach it in about two years; desktop writes against a large rating do not. Illustrative values.

Two limits on what I can say: I have no data on drives with the lowest ratings, and I haven’t measured a creator’s workload. And wear is only one way a drive fails. Meza’s finding that failures do not climb steadily with wear is the subject of the myth that an SSD fails with no warning.

What to do

Look at your own drive instead of worrying about it. Read Data Units Written and multiply by 512,000 bytes, then read Percentage Used and Available Spare. Divide your total by the days the drive has been powered to get a daily rate.

Multiply that rate by 730. If the result is a small fraction of the TBW on your drive’s data sheet, two years will not wear it out.

What to do

Check your own drive in four steps

From the SMART log to the data-sheet rating (no values: yours come from your drive)

Four stacked steps joined by arrows. One, read Data Units Written and multiply by 512,000 bytes to get total host writes. Two, divide by the days the drive has been powered to get a daily rate. Three, multiply the rate by 730 days to get the writes two years would add. Four, compare that with the TBW on the data sheet. If it is a small fraction, two years will not wear the drive out. A side note says to read Percentage Used and Available Spare as well.01 READData Units Written from the SMART logMultiply by 512,000 bytes: your total host writes02 DIVIDETotal writes ÷ days the drive has been poweredYour daily write rate03 MULTIPLYDaily rate × 730 daysThe writes that two years would add04 COMPAREAgainst the TBW on your drive’s data sheetIf it is a small fraction, two years will not wear it outAlso read Percentage Used and Available SpareSteps you work outData-sheet rating
Read the writes, turn them into a daily rate, multiply by 730 and compare with the TBW. Also read Percentage Used and Available Spare. Illustrative values.

If you move hundreds of GB a day, check the rating before you buy instead of assuming a small drive will last. For ordinary desktop use, leave the drive alone. The same arithmetic answers the pagefile worry, and it keeps the page file where it is.

Sources

Primary is the original paper, standard or datasheet. Secondary is a review, a vendor summary or a news report. Measured is my own test data.

Show all 9 sources, 7 primary