SSD Write Endurance 25nm Vs 34nm

I've updated the info in post#1 on the M3P, an extremely exciting drive, lets see how it compares to the Samsung.

@Ao1
I've been looking for data on the Kingston V100+ and it is there, I looks like we couldn't decide on whether the attribute in question really was an MWI counter, anyways I did put it in the table. TiB written when it ran out of MWI would mean ~3300 so it looks to be correct.

I've got logs for my drives from the day I started using the log, January 9th this year.
I'll find the missing "points" for the X25-V, shouldn't be that much of a job if we do our own drives.

An overview of all drives that are not running anymore.

Attachment 127140

The 460 is one of the drives that we never really decided/agreed on when MWI was exhausted.
(Johnw, looking back and vs the 830 attributes, 60TiB looks to be a very low figure for that drive)

Attachment 127142

Attachment 127141

Quote:

---

Originally Posted by Christopher

Ao1,

V4 128GB Intel 29F64G08ACME3
Octane 128GB Intel 29F64G08ACME2

---

I can’t find a data sheet for that either of this NAND types, but onethreehill has done an excellent job of collecting data on controllers and NAND.

http://forums.storagereview.com/inde...eviews-thread/

According to that link the NAND in the V3/ Octane has been used in a number of different drives. The Octane also used Hynix NAND and there have been widespread reports of premature relocated sectors with Hynix NAND. So the issue is evident on NAND from two different suppliers.

Intel 29F64G08ACME3
Kingston SSDNow V+200
Zalman F1 120GB
Team Xtreem S3

Intel 29F64G08ACME2
Corsair Force Series GT 120GB
Mach Xtreme DS Turbo 120GB
Silicon Power V30 60GB
Silicon Power V30 120GB

Quote:

---

Originally Posted by Anvil

I've got logs for my drives from the day I started using the log, January 9th this year.
I'll find the missing "points" for the X25-V, shouldn't be that much of a job if we do our own drives.

---

That would be great. There is a lot of info missing in the tables in the first post. It would be great to see a chart showing how relocated sectors occurred for each drive and also a calculation of WA/WL based on when the MWI expired (if sufficient SMART data is available).

Quote:

---

Originally Posted by Ao1

I can’t find a data sheet for that either of this NAND types, but onethreehill has done an excellent job of collecting data on controllers and NAND.

http://forums.storagereview.com/inde...eviews-thread/

---

The same info is listed in the storage section here as well.

Lol, that will teach me for only hanging around in the storage section.

The X25-M G1 used 50nm NAND and Intel claimed a write amplification factor of 1.1. The best possible is 1, so from 2008 when the X25-M G1 came out there has been near zero scope for improvement in f/w algorithms to further reduce WA.

The only way to get below 1 is to use compression. To get closer to 1 the only other option is to use DRAM to optimise how writes are placed on the NAND.

Looking at it that way it makes more sense to me now why Intel have switched to SF and why drives with no compression are having to start to use large DRAM caches to offset reduced P/E cycles (which Intel have always avoided).

It could be that drives with large DRAM caches are negatively impacted by the sustained writes that occur in the endurance workload as opposed to normal workloads that occur in real life. That does not explain the V3 or Octane however.

The 830 has a relatively large DRAM cache, and it doesn't seem to be adversely affected. I think Intel just went with SF as a hedge against smaller lithography. When they started with SF, they probably ha no idea what 20nm was going to look like in production form (with respect to longevity). At least in Intel's case, SF seems to be doing its job in that respect, but i'm not super stoked about 20/19nm regardless of what controller it's bolted too.

Assuming P/E cycles are calculated correctly with the 830, your drive hit 827,911 @ MWI 1.

Capacity *P/E spec / ((WA) * (WL)) = Total theoretical write capability

256 *5,000 = 1,280,000/ 1.54

WA & WL = ~ 1.55

I'll work it out for a drive with no cache later.

This was the post where mwi reached 1 for the Kingston V+100. Link Read error rate and reallocated sectors count was at 0. They didn't move when the ssd died.

M4v1 reached wmi=1 without a change of the Read error rate and reallocated sectors count at 172.3671 TiB. The first Read error rate came at 700.4629 TiB
M4v2 reached wmi=1 without a change of the Read error rate and reallocated sectors count at 174.3919 TiB. At 951 TiB it still have none.
Intel X25-M G1 reached wmi=1 without a change of the Read error rate and reallocated sectors count at 147,5687 TiB.. The first reallocated sector came at 308,22 TiB.

The 830 is supposed to be using 3K PE flash, but MWI was based on more like 3.6K.

Todays update:

m4
951.7772 TiB
4006 hours
Avg speed 74.35 MiB/s.
AD gone from 69 to 66.
P/E 16394.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=492199

Intel X25-M G1 80GB
655.58 TiB
23318 hours
Reallocated sectors : 162
Available Reserved space: 90
MWI=124
MD5 =OK
42.79 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492203

Intel X25-E 64GB
131.75 TiB
405-30=375 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.07 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492201

Quote:

---

Originally Posted by Christopher

The 830 is supposed to be using 3K PE flash, but MWI was based on more like 3.6K.

---

There are a lot of assumptions with the Samsung due to a lack of proper SMART info and info on the NAND. The X25-V is a bit easier:

X25-V
MWI 1 @ 187,627 GB
40 *5000 = 200,000 GB
WA & WL = ~ 1.06

Here is a quick summary of drives with good SMART info. I’m going to guess that the P/E count for the Chronus was 3K not 5K giving a WA factor of 0.85, which seems more logical considering 46% compression was used.

M4 64 GB (25nm) = 176,128 – 64*3000 = 320000/ = 1.09 (or 1.8 with 5K P/E)
Intel X25-M G1 80 GB (50nm) = 150,528 – 80*10,000 = 800000/150528 = 5.31 (No TRIM)
Intel 320 40 GB 25nm = 194,560 - 40*5000 = 200,000/ 194,560 = 1.03
C300 64 GB (34nm) = 301,056 - 64*5000 = 320,000/301056 = 1.06
Chronos 60 GB (32nm) = 218,112 – 60*5000 = 300000/218112 = 1.37 (or 0.85 with 3K P/E) (46% compression)
Intel 520 60 GB = 429056– 60*5000 = 300000/429056= 0.69 (46% compression)
Intel X25-V 40GB = 187,627 – 40*5000 = 200000/187,627 = 1.06


Edit:

WA for the Intel 320 is slightly lower than the X25-V as expected, but getting any lower without compression must be close to impossible, so as 1,000s of P/E cycles disappear with every reduction in NAND geometry there is no way of avoiding a reduced life span.

Intel 330 120GB

40.72TB Host writes
Reallocated sectors : 05 0
Available Reserved Space : E8 100
MWI 97
[F1] Total LBAs Written 1334448
[F2] Total LBAs Read 22623 // no movement
[F9] Total NAND Writes 29400GB
POH 106
MD5 OK

122.48MiB/s on avg (~33 hours)

http://www.ssdaddict.com/ss/Endurance/I330_MWI.png


--

Kingston SSDNow 40GB (X25-V)

988.64TB Host writes
Reallocated sectors : 05 46
Available Reserved Space : E8 99
POH 8854
MD5 OK

34.30MiB/s on avg (~33 hours)

--

Attachment 127143

The SMART info on my 830 is fine. WLC works like it should, incrementing every 230GB, which was almost exactly 4x the 64GB Turbos. I believe it hit MWI 1 at 3620PE cycles. In any event, it's not 5K.

Assuming perfect wear leveling, PE count should increase every 256GB. It doesn't have perfect WL, so we can go by PE count (which has been the paragon of consistency this time around) 256/230 = 1.113

3600 * 256GB = 921,600

921,600 / 1.113 = 828,032GiB


I'm not really sure where I'm going with this, but ~1.1 is really where most decent drives should be (that aren't SF, but I suspect you might include them as well) with TRIM and whatnot.

The 830 is not suffering from 1.5xx WLE/WA no matter what.

The thing is that some of the firmware-enhancements may have altered and bettered both WA and WL.
Some of the drives have had the fw updated multiple times during the test, that leaves some uncertainty about how the drive could have performed if it was using the later/best fw since day 1.
Well, I'm going to update to the latest fw when/if it shows up, as would I in real life.

Anyways, it is interesting seeing what the figures look like as they should be close.

The 01FW for the 830 is a sack full of pain where WA is concerned. I think the V4s WA got markedly worse with 1.4FW. Most drives don't get that much of a bump one way or the other, and it's hard to know what's going to happen before you flash.

I know that the M3P's GC got tweaked on 1.03 FW, but I didn't see much difference. I did a lot of IOmeter and power consumption testing for several hours before puttin the M3P to work.

1.5 PB?!! That Samsung's doing great :shocked:

Congrats on becoming a mod Anvil, when did that happen?

The Torqx 2 had its first bad block at approximately 40600 GiB, with 1677 average NAND cycles, 2539 max NAND cycles.

The Vertex 4 had its first bad block at 294.27 TiB Host writes.

If you have an octane/petrol or vertex 4 and your drive gets a bad block, you better have a backup!

The Kingston (X25-V) had reallocation's (1) from the get-go.

I'm sending a list of all reallocation's to Ao1. (until SmartLog was introduced)

Quote:

---

Originally Posted by Ao1

Edit:

WA for the Intel 320 is slightly lower than the X25-V as expected, but getting any lower without compression must be close to impossible, so as 1,000s of P/E cycles disappear with every reduction in NAND geometry there is no way of avoiding a reduced life span.

---

Yes there is, multiple techniques:

a) More ECC, so the wearing effect is less apparent and takes longer to degrade the capacity of an NAND cell to hold data.
b) Gentle programming/erase techniques. Not entirely sure if this is possible, but multiple companies claim to be doing stuff like this ... it will trickle down to consumer SSDs as needed.
c) Larger capacity SSDs. As lithography shrinks, capacity of drives will increase with mostly offsets the reduction in endurance. It is nice to dream of a 512gig drive in 50nm NAND, but outside of the odd deal, no normal person can afford it.

EEC deals with correctable errors and as NAND geometry shrinks, instances of correctable errors increase exponentially. A correctable error does not necessarily mean the NAND cell is on its way out. Any improvements that may be available in the future have to be offset by the continuing growth of page sizes as geometries shrink. I really can’t see anything that is going to reduce WA below what it is already (without compression), especially if page file sizes continue to grow, but then again I’m not a NAND engineer.

Quote:

---

Originally Posted by Ao1

EEC deals with correctable errors and as NAND geometry shrinks, instances of correctable errors increase exponentially. A correctable error does not necessarily mean the NAND cell is on its way out. Any improvements that may be available in the future have to be offset by the continuing growth of page sizes as geometries shrink. I really can’t see anything that is going to reduce WA below what it is already (without compression), especially if page file sizes continue to grow, but then again I’m not a NAND engineer.

---

Error rate also increases as the NAND becomes more worn. Having stronger ECC means you can apply more wear to the NAND cells before they become too damaged to reliably correct. This is one of the keys ideas behind Intel's HET-NAND.

Bad/weak block identification also seems to be an important key to SSD long life. Intel's own controller seems to have this spot on, while I'm more skeptical of the crucial and sandforce drives. The everest (and everest 2) controllers probably need more work, something seems a bit iffy about how bad blocks occur on octane and vertex 4 drives.

I agree that WA doesn't really any room to improve anymore ... although working block dedup could certainly improve it a bit more.

I've actually moved the two drives out of the endurance rig and into my main desktop. I want to see what happens over the next week, as I noticed that the drives seem to be not in-considerably faster.

After 21 hours, the M3P is at 270MB/s and the 830 is at 303MB/s. I'm probably hallucinating, but I feel like there is something preventing the drives from running quite as fast as they should. Both rigs are on 10.6.1002, one H67 and Z68.

Perhaps I imagined it, but we'll see.

Quote:

---

Originally Posted by Christopher

Both rigs are on 10.6.1002, one H67 and Z68.

---

I am using 11.1.0.1006 on my Z77. Seems to be working pretty well.

Could power management be a factor.

Maybe you are wearing out the SATA cables with all the transferred data :D

Quote:

---

Originally Posted by canthearu

I am using 11.1.0.1006 on my Z77. Seems to be working pretty well.

Could power management be a factor.

Maybe you are wearing out the SATA cables with all the transferred data :D

---

Maybe all those PB of host traffic are wearing out the PCH... but no, I don't think so. Not sure what it is, but when I was doing preliminary testing I would use my desktop, and it would be around 270 avg for the M3P. I'd put it in the e-rig, and it would do 240ish MB/s. Both seem to be doing much better, but it will be a few days before I know for certain.

Plextor M3P 128GB Day 1

27,386.66 GiB
26.74 TiB

269.65 MB/s Average

25 Hours

Rellocated Event Count 0
--------------------------------------------

Samsung 830 256GB Day 70

1,683,657.62 GiB
1,644.20 TiB

304.48 MB/s Average
1667 Hours

7260 Wear Leveling Count
MWI 1

6/0 Erase/Program Fail
Used Reserved Block Count: 12/24572 sectors

--------------------------------------------

The M3P is doing 269MB/s avg after 25 hours, the 830 is doing a staggering 304MB/s. We'll see where they settle.

Are the rigs set up differenty?
(drivers, AV scanning, ...)

The speed of the M3P almost looks too good to be true, how many days will it last based on that speed. (based on i.e 3K P/E cycles)

Quote:

---

Originally Posted by Anvil

Are the rigs set up differenty?
(drivers, AV scanning, ...)

The speed of the M3P almost looks too good to be true, how many days will it last based on that speed. (based on i.e 3K P/E cycles)

---

The rigs are very similar, neither has AV or anything like that -- especially the endurance rig, which is about as stripped down as a Win7x64 install can get. The instantaneous speeds are higher, not just the average.

The M3P 128GB is a fantastic drive. Having 32 dice helps. It maxes out at 350MB/s writes at just about every transfer size.

Attachment 127146

Attachment 127147

I think the 128GB 830 would be almost as fast, but the 830 is a little more inconsistent. The M3P does 322MB/s through the entire loop just about.

The two drives could be fast enough that other factors are coming into play with regards to speed. At 269.73MB/s avg, you'll get 22,758GiB a day.Each day the drive will use about 197 PE cycles based on 1.1 WA

Intel 330 120GB

46.92TB Host writes
Reallocated sectors : 05 0
Available Reserved Space : E8 100
MWI 96
[F1] Total LBAs Written 1537505
[F2] Total LBAs Read 22623 // no movement
[F9] Total NAND Writes 33879GB
POH 144
MD5 OK

122.66MiB/s on avg (~48 hours)

--

Kingston SSDNow 40GB (X25-V)

990.32TB Host writes
Reallocated sectors : 05 46
Available Reserved Space : E8 99
POH 8869
MD5 OK

33.99MiB/s on avg (~48 hours)

Todays update:

m4
957.0306 TiB
4027 hours
Avg speed 74.35 MiB/s.
AD gone from 66 to 63.
P/E 16483.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=492268

Intel X25-M G1 80GB
658.64 TiB
23339 hours
Reallocated sectors : 162
Available Reserved space: 90
MWI=124
MD5 =OK
42.82MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492272

Intel X25-E 64GB
138.93 TiB
426-30=396 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.07 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492270

Intel 520 60GB - Day 95

Drive hours: 2,227
ASU GiB written: 705,925.67 GiB (689.38 TiB)
Avg MB/s: 93.40 MB/s
MD5: OK

Host GB written (F1): 710,944.63 GiB (694.28 TiB, 22750228 raw)
NAND writes (F9): 503,298 GiB (491.50 TiB)

Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 100 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 1

Avg speed on the 830 is down 2%, M3P is up by 1%.

After 37 hours, it's just about blown through 10% of the PE cycles! Exciting.

I wish the MWI implementation on the Plextor wasn't so damn lazy.

I haven't gotten to test mine yet, I've updated the firmware so they are ready.

Have you got a recent screenshot showing the M3Ps SMART status/values?

Here are a couple of charts showing relocated sector events for the intrepid X25-V. I had forgotten that relocated sectors turned up on the X25-V before the MWI had expired. It follows the bath tub curve quite well. (Infant mortalities, stability and then progressive failure).

Attachment 127159

Attachment 127160

I'm really hoping it will appear to be 5K P/E(Toshiba Type B 24 nm T-Nands).. sadly corsair performance pro's smart values arent any different than plextors

I'm not sure how upset I would be if I bought a Performance Pro and I got 24nm instead of 32nm. While it is uncouth to swap flash without saying so, the 24nn uses much, much less power. The M3P maxes out at 2.6w, and it doesn't even get above ambient during endurance testing. If it puts in a halfway decent showing, the 24nm might be what you want.

We will see how the M3P does, but previous drives using Toshiba toggle have not done well at all (Samsung's Toggle appears to be a different story).

Quote:

---

Originally Posted by Anvil

I haven't gotten to test mine yet, I've updated the firmware so they are ready.

Have you got a recent screenshot showing the M3Ps SMART status/values?

---

Certainly. I'll post it later, but all current/worst values are nominal. Only power on/cycles and host writes are changing.

I'll post it when I get home.

Thanks Ao1,
Hopefully they'll be able to make "drives" like that again.
It has been uneventful except for enduring more than any other drive, so far.

Christopher,
Just wait until something interesting happens.

M3P Smart
Attachment 127163

So power cycles, power on hours, unsafe shutdown and host writes are the only values which increment so far.

I expect if/when a block goes bad MWI and reallocations will change.

All current/worst values are still at 100.

474556*64MiB that's close to 29TiB

I expect CDI and or others will pick up on the writes attribute, lets hope reallocations won't happen for a while, at the current speed it probably won't take more than a few weeks though.

Quote:

---

Originally Posted by Anvil

474556*64MiB that's close to 29TiB

I expect CDI and or others will pick up on the writes attribute, lets hope reallocations won't happen for a while, at the current speed it probably won't take more than a few weeks though.

---

That was a shot from last night. It's currently at 714341 (44,646 GiB). I just didn't want anyone thinking that the attribute didn't work correctly (it does -- B1 RAW * 64 = host writes MiB).

That M3P is in a real hurry. I'm not sure where it is in a hurry to get to, but where-ever it is going, it won't take very long.

Quote:

---

Originally Posted by canthearu

That M3P is in a real hurry. I'm not sure where it is in a hurry to get to, but where-ever it is going, it won't take very long.

---

It's going to Hell, and quickly at that. I'd expect to maybe see a reallocation in around two weeks -- somewhere near 3000PE cycles or so. I hope I'm wrong though. Fortunately for me, I usually am.

Maybe Plextor's price premium is in part due to higher binned NAND, perhaps analogous to the Kingston HyperX 5K? Doubtful, but I remain hopeful. I think they just charge more because it's fast.

--------------------------------------------

Plextor M3P 128GB Day 2

49,245.08 GiB
48.09 TiB

271.21 MB/s Average

48 Hours

Rellocated Event Count 0

Attachment 127177

--------------------------------------------

Samsung 830 256GB Day 72

1,707,352.20 GiB
1,667.33 TiB

300.36 MB/s Average
1694 Hours

7260 Wear Leveling Count
MWI 1

6/0 Erase/Program Fail
Used Reserved Block Count: 12/24572 sectors

Attachment 127178
--------------------------------------------

I've been looking at the SMART data on the 330 and it does not look to be 3K NAND. (it could still be though)

From what I can see, Raw NAND writes points to MWI exhaustion at about 5K which means ~590TiB of NAND writes and 835TiB of Host writes.
(based on the first 5 MWI movements, the next few days will tell whether it sticks, I'm recording every 10 minutes so the change is not immediately recorded)

Quote:

---

Originally Posted by Anvil

From what I can see, Raw NAND writes points to MWI exhaustion at about 5K which means ~590TiB of NAND writes and 835TiB of Host writes.

---

Heh, so basicly twice the Intel 520 60gig drive.

Looks like you might win this one :P

It looks that way :)

It's early days yet, I'm happy with the 330 so far, throughput is about where I expected it to be.

Todays update:

m4
963.7975 TiB
4053 hours
Avg speed 74.36 MiB/s.
AD gone from 63 to 59.
P/E 16598.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=492380

Intel X25-M G1 80GB
662.57 TiB
23365 hours
Reallocated sectors : 162 to 163
Available Reserved space: 90
MWI=124
MD5 =OK
42.86 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492384

Intel X25-E 64GB
148.12 TiB
452-30=422 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.03 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492382

I'm kinda excited about the 330... I wonder if maybe it's just cheaper to use Intel's stash of NAND? Maybe it really is just Cherryville with 300i and not 400i FW... and no other differences.

I'd be happy just to get 5K PE cycles out of the M3P, as fast as it is.

Quote:

---

Originally Posted by Christopher

I'm kinda excited about the 330... I wonder if maybe it's just cheaper to use Intel's stash of NAND? Maybe it really is just Cherryville with 300i and not 400i FW... and no other differences.

I'd be happy just to get 5K PE cycles out of the M3P, as fast as it is.

---

I hope you get 10K ill be happy to know mine will last

--------------------------------------------

Plextor M3P 128GB Day 3

72,655.01 GiB
70.95 TiB

273.05 MB/s Average

72 Hours

Rellocated Event Count 0

--------------------------------------------

Samsung 830 256GB Day 73

1,732,685.11 GiB
1,692.07 TiB

300.05 MB/s Average
1717 Hours

7525 Wear Leveling Count
MWI 1

6/0 Erase/Program Fail
Used Reserved Block Count: 12/24572 sectors

Attachment 127221
--------------------------------------------

The pace of both drives is really phenomenal. We'll see where the 830 ends up after more than 72 hours, but switching both drives into the other rig seems to have resulted in tangible and worthwhile performance increases. The top current speeds are just higher, resulting in higher averages.

The 830 was only doing 282 MB/s Avg four days ago. An extra 20MB/s is nothing to sneeze at.

EDIT
10,000 PE cycles on the Plextor would probably be somewhere around 1.09PiB

The M3P is already ahead of the 330, if it can keep up the pace until the end I'd be impressed.

I wonder if there are plans on using IMFT 5K NAND, would be very interesting on a Plextor.

The forum doesn't allow for searches of three characters, does anyone know/remember if the Intel 320 series (preferably 120 GB) was tested here?

Intel 330 120GB

66.96TB Host writes
Reallocated sectors : 05 0
Available Reserved Space : E8 100
MWI 94
[F1] Total LBAs Written 2194022
[F2] Total LBAs Read 22623 // no movement
[F9] Total NAND Writes 48334GB
POH 191
MD5 OK

122.68MiB/s on avg (~95 hours)

--

Kingston SSDNow 40GB (X25-V)

995.75TB Host writes
Reallocated sectors : 05 46
Available Reserved Space : E8 99
POH 8916
MD5 OK

33.59MiB/s on avg (~95 hours)

Quote:

---

Originally Posted by [XC] Oj101

The forum doesn't allow for searches of three characters, does anyone know/remember if the Intel 320 series (preferably 120 GB) was tested here?

---

It was one of the original drives that started this test.
One_Hertz tested a 320 40GB, a great drive, my drive outlasts it but that's 34nm NAND for you.

You'll find a bit of info in the first post, it failed this January at 685TiB written, outstanding performance imho :)

Todays update:
I got a big update today.

First:
I got the Mtron from GullLars today. I'll be start testing it in a couple of days after I've done some maintenace on my rig. I'll post some screenshots tomorrow.

Second:
I updated some drivers on the rig today and a round of windows update. After the restart I noticed that the icon for the ASU G1 was strange. Trying to open it failed and when I looked at the ssd I got this error message.

http://www.diskusjon.no/index.php?ap...tach_id=492524

Checking CDI I the G1 was still being detected but available reserved space had dropped from 90 til 89 and reallocated sectors gone from 163 to 169.
http://www.diskusjon.no/index.php?ap...tach_id=492523

In disk management the ssd is shown as unformated and I had to format it to make it work again.
http://www.diskusjon.no/index.php?ap...tach_id=492522

I copied back all the files and the correct setings for ASU. Since all data was lost I have to relay on host write in smart to keep track of writes.
Before I started up ASU I checked CDI and now a lot had happend. Available reserved space had dropped from 89 to 78 and reallocated sectors had dropped from 169 to 73.
I refreshed CDI and while I looking at it the value increases. I adjusted smartlog to update every minute and here are the change and the time. I removed all timeslots that didn't change.

09:57:31.203 163
10:28:08.472 166
10:31:03.354 169
11:21:12.077 73
11:22:12.824 81
11:23:13.617 86
11:24:16.719 86
11:25:19.119 90
11:26:18.134 94
11:28:20.517 95
11:29:21.247 97
11:32:25.219 98
11:44:36.236 100
11:47:38.179 103

Looks like I took a out a big chunck of blocks but why this strange behavior on the reallocated sectors I have no explanation for. I think the next days will be exciting if the G1 continues or looses more sectors.

m4
968.9236 TiB
4082 hours
Avg speed 74.50 MiB/s.
AD gone from 59 to 55
P/E 16710.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=492530

Intel X25-M G1 80GB
666.52 TiB
23392 hours
Reallocated sectors : 163 to 163 to 73 to 103
Available Reserved space: 90 to 89 to 78
MWI=124 to 116
MD5 =OK
43.81 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492529

Intel X25-E 64GB TiB skrevet med en snittfart på MiB/s. SSDen er testet i (
157.16 TiB
480-30=450 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99 to 98
MD5 =OK
99.71 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492531

Finally the E changes mwi from 99 to 98. It happened at 152,3694 TiB according to smartlog. It means that mwi=1 will happen at almost 15 PiB.....:shocked: :shrug:

What happened with the G1 (I think) is that the counter wrapped around from 255 back to 0,

So reallocated sectors is now 103+256 = 359. But the G1 is looking a bit hurt ... showing same sort of symptoms as my Torqx 2 did.

I wonder why I lost all data on the G1. That was the strangest thing...

That is exciting, B.A.T. I wonder if maybe the drive dropped too many blocks at one time and the drive couldn't recover them, corrupting the partition (??)

The Intels don't keep track or read/erase/program failures unfortunately.


What kind of MTRON are you doing?

It looks like it. I think I'll do an retention test at 700 TiB to see whats going on.

It's the brother of the last Mtron I tried. GullLars had two i r0. It's a MTRON Pro SSD 32GB

--------------------------------------------

Plextor M3P 128GB Day 4

96,000.12 GiB
93.75 TiB

274.34 MB/s Average

96 Hours

Rellocated Event Count 0
Attachment 127252

--------------------------------------------

Samsung 830 256GB Day 74

1,757,421.07 GiB
1,716.38 TiB

303.08 MB/s Average
1741 Hours

7632 Wear Leveling Count
MWI 1

6/0 Erase/Program Fail
Used Reserved Block Count: 12/24572 sectors

--------------------------------------------

The combined average speed for both drives is 577.42MB/s. That's a not inconsiderable amount of data going through the board every second.

Wow, I was just thinking to myself that the 830 had gone awhile without another block fail, and lo! 45 seconds later, another went bad.

7 Erase Fails, 7 runtime total blocks used, 28672 Reallocated Sector Count

That's 14MiB if you're keeping score at home (out of 262,144 MiB on the drive).

Intel 520 60GB - Day 98

Drive hours: 2,298
ASU GiB written: 729,146.54 GiB (712.06 TiB)
Avg MB/s: 93.07 MB/s
MD5: OK

Host GB written (F1): 734,281.25 GiB (717.07 TiB, 23497000 raw)
NAND writes (F9): 519,818 GiB (507.63 TiB)

Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Raw Error Rate (8B): 100 normalised
Avaliable Reserved Space (AA): 100 normalised
Media Wearout Indicator (E9): 1

On the topic of data retention .... it is time for a retention test on my Intel 520 ... It has exceeded 500TiB in NAND writes (approx 8k NAND cycles). Will be off and disconnected for 3 days.

canthearu
Thanks for the update!
Could be an exciting 3 days :)

B.A.T
A few reboots per month might catch such issues earlier, I reboot once a month and often as a result of the Tuesday windows updates.
The G1 is really getting some beating, no TRIM no nothing, wouldn't surprise me at all if it start showing signs of weakness.
(or maybe it's the curse of the MTRON ;))

I'll post an update later tonight, the X25-V is very close to 1PB, 8-9 hours or so.

Attachment 127261

Plextor released new firmware for M3s, 1.04.. not much info what it changes

http://www.goplextor.com/asia/index....gory&catid=147

EDIT: ok i think i found it..
http://www.abload.de/img/desktop_2012_05_31_20z87ou.png

Guys, I know this would be a pain, but would it be possible to compile a chart of all the drives tested since the inception of this thread?

Quote:

---

Originally Posted by Kain665

Guys, I know this would be a pain, but would it be possible to compile a chart of all the drives tested since the inception of this thread?

---

There is a chart of the past drives in the first thread, right above a chart of the current drives.

Christopher, I have a Samsung 830 256GB and have been following this thread closely in recent days... Would it be safe to say that the MWIs for most of these drives are 1. arbitrarily chosen by the manufacturers and 2. extremely conservative based on these endurance tests? Also, how far do you think the 830 will go given the current low error count? 3 PBs? 10 or more PBs?

I had been using a 160GB Intel X-25M G2 since 2009 and calculated that on average I was writing roughly 6-7GB per day over the period of a couple years (I mostly use it for documents and web surfing and some light gaming, hibernation/hybrid sleep is off, it's on for about 8 hours out of every 24, with maybe 4 days off per month average.)

I expect usage for my Samsung 830 to be about the same. Assuming that I'll write 7GB per day, and that I can get roughly 2PB of writes out of this drive (which currently appears extremely likely), it would work out to ~820(!) years of usage.

Now, I get that for enterprise workloads like database work you might be doing a whole lot more writing, but even if you turned over the entire drive (238GB) every day, you'd still get around 24 years of use out of this drive, (again, assuming it craps out at 2PB.) I'd have to be writing at least a terabyte every single day to ever get close to thinking about this wearing out in a reasonable technology upgrade timeframe. My guess is that 99.9% of these drives will inevitably end up in a landfill due to obsolescence with only a small fraction of their writes ever being used.

Todays update:

m4
974.8412 TiB
4105 hours
Avg speed 74.58 MiB/s.
AD gone from 55 to 52
P/E 16810.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=492620

Intel X25-M G1 80GB
669.92 TiB
23416 hours
Reallocated sectors : 103 to 104
Available Reserved space: 78
MWI= 116 to 114
MD5 =OK
43.07 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492621

Intel X25-E 64GB
165.15 TiB
504-30=474 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI= 98
MD5 =OK
100.12 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492619

I'll update you on the Mtron in 30 min. Need to check something first.

@Anvil
The last reboot was when I entered the E into the test-rig. Maybe the Mtron jinxed it :D Everything looks normal no so we'll just have to wait and see.

Mtron Pro 32GB SLC

Here are the smartvalues
Attachment 127266

The nand
Attachment 127267

The controller
Attachment 127268

And the spec
Link Link

I need some help to translate the raw value in total erase count.

B.A.T

Record the raw value before and after writing a 1GB file.
(ASUs sequential [4MB seq] test will do that)

Two SLCs :)
I hope the MTron behaves this time

--

It's getting close.
Attachment 127269

(a bit busy downloading the new stuff from MS but will post an update when it gets past 1PB)

Gordo,

The MWI for most drives is extremely conservative, but that helps take into account the fact that some drives will not make it as far as other drives (if you had two identical drives, under an identical workload, they probably wouldn't die at exactly the same time). The way PE cycle ratings are generated is extremely pessimistic, and a little arbitrary, but there are reasons they do it that way.

For a 830 only using 1 PE cycle a day (based on ~3600 PE cycles) it would take 9.8 years give or take to get to MWI 1. It's unrealistic to expect the drive to last that long though, as generally speaking, it's going to be something else that kills the drive.

I would hate to venture how far my 256GB 830 will go, I've pretty much been wrong on every prediction in the past. The 830 has been slowly marking blocks as bad, and that's a good thing. That means its doing what it's supposed to. What you don't want to see is many reallocations occurring within a short period of time - you want them to be spread out. The 256GB 830 used 107 PE cycles yesterday. The 128GB Plextor M3P I'm also testing writes almost as many GB per day, but it uses almost 2x the PE cycles. So all other things being equal, the M3P 128GB should die ~2x as fast. There are many other variables, making it hard to tell for certain -- that's why I'm testing them.

You never know.



I would say that the G2 Intel and the Samsung 830 aren't going to be obsolete any time soon. And if people are going to be dumping them in landfills in a couple years mostly unused, I wish someone would tell me first ;)

Thanks Anvil. I'll try that in the weekend. First I need to do an SE and some maintenace on my rig. I run the benchmark and got good read numbers but write was far off.

Almost there with the V. I'll pass 1 PiB in late sunday or early monday.

B.A.T. --

I'm excited -- I love those damn irritating MTRONs.


The erase count is literally the number of erases (I think it's in 1MB chunks). My 16GB MTRONS would decrease MWI around every 15 000 000 RAW. Unfortunately, because the drive is always doing GC and wear leveling the number is always increasing even if you're not writing to it. You could fill the drive to 100% look at before and after SMART shots, then erase the drive. The Samsung 51nm SLC is rated for 100K PE cycles, so 1 MWI should be 1000 PE cycles. 1000 * 32 768 MB = 32 768 000. Something like that, anyway.

The maximum raw value is 3 200 000 000 for the 32GB, should be 1 600 000 000 for the 16GB (but I have no way of verifying what the hell happens when you get that far).

Your drive is probably ~98.4 MWI if you want to think about it that way.

Writing a 1GB file to the PRO isn't going to tell you all that much. If you do it a couple times, it will be different each time.

I also think I have the .18R FW for your drive, but I would avoid flashing it like the plague. It's not like 4K RWs are going to skyrocket from 0.45MB/s to 0.50MB/s. But I get 46MB/s QD1 Random Reads with my PROs though. So that's nice, and you should be able to get a high avg speed.

Intel 330 120GB

82.64TB Host writes
Reallocated sectors : 05 0
Available Reserved Space : E8 100
MWI 92
[F1] Total LBAs Written 2707960
[F2] Total LBAs Read 22623 // no movement
[F9] Total NAND Writes 59652GB
POH 228
MD5 OK

122.70MiB/s on avg (~132 hours)

--

Kingston SSDNow 40GB (X25-V)

1000.01TB Host writes
Reallocated sectors : 05 46
Available Reserved Space : E8 99
POH 8953
MD5 OK

33.49MiB/s on avg (~132 hours)

Quote:

---

Originally Posted by Anvil

Kingston SSDNow 40GB (X25-V)

1000.01TB Host writes
Reallocated sectors : 05 46
Available Reserved Space : E8 99
POH 8953
MD5 OK

33.49MiB/s on avg (~132 hours)

---

Ha Ha!

Excellent :clap:

Quote:

---

Originally Posted by Anvil

[B]
Kingston SSDNow 40GB (X25-V)

1000.01TB Host writes
Reallocated sectors : 05 46
Available Reserved Space : E8 99
POH 8953
MD5 OK

33.49MiB/s on avg (~132 hours)

---

Quote:

---

Originally Posted by Christopher

Ha Ha!

Excellent :clap:

---

Break out the champagne it is party time!!!!! :up:

Quote:

---

Originally Posted by Christopher

For a 830 only using 1 PE cycle a day (based on ~3600 PE cycles) it would take 9.8 years give or take to get to MWI 1. It's unrealistic to expect the drive to last that long though, as generally speaking, it's going to be something else that kills the drive.

---

Really? What else would kill it? An electrical surge? A blown capacitor? The drive controller chip wearing out?

As far as PE cycles go, would you say that your drive is indicative of what one should expect with Samsung 830s? With your 830 at ~7600 WLC, doesn't that mean that most cells have more or less lasted to about double the manufacturer expected lifetime so far? I assume a core assumption in all this endurance testing is that there's not much variation between drives of the same type at least as far as PE cycles go, which is why you feel comfortable making basic conclusions using only a single drive of each type. If there was a lot of PE cycle lifetime variation between two drives of the same model (say your 830 is a real outlier, and mine is much closer to manufacturer speced PE counts), I would think this whole exercise would not be particularly useful as far as forming generalized conclusions about what a particular drive should be expected to do.

Also, for a given write load, doesn't increasing the size of the drive quickly make up for say the difference between 3k and 5k PE cycle NAND? In other words, if you have a massive write load application, just pick a bigger drive. Alternately, can't manufacturers just move to larger and larger SSDs to account for lower PE Counts associated with smaller and smaller smaller process NAND chips (all else being equal)?

Quote:

---

Originally Posted by Christopher

What you don't want to see is many reallocations occurring within a short period of time - you want them to be spread out

---

Right, but once the NAND is beginning to reach its actual physical limits, assuming you have an excellent wear leveling algorithm, wouldn't one expect that the reallocations actually do start to happen almost all around the same time as each NAND cell reaches its limit?

Quote:

---

Originally Posted by gordo

Really? What else would kill it? An electrical surge? A blown capacitor? The drive controller chip wearing out?

As far as PE cycles go, would you say that your drive is indicative of what one should expect with Samsung 830s? With your 830 at ~7600 WLC, doesn't that mean that most cells have more or less lasted to about double the manufacturer expected lifetime so far? I assume a core assumption in all this endurance testing is that there's not much variation between drives of the same type at least as far as PE cycles go, which is why you feel comfortable making basic conclusions using only a single drive of each type. If there was a lot of PE cycle lifetime variation between two drives of the same model (say your 830 is a real outlier, and mine is much closer to manufacturer speced PE counts), I would think this whole exercise would not be particularly useful as far as forming generalized conclusions about what a particular drive should be expected to do.

---

The number one problem is firmware rendering the drive unusable, but you can short them out if you do something stupid (I did that to an MTRON I was testing). The 830 is probably pretty indicative of most -- most of the flash is pretty much identical, at least in so far as it will far exceed what it's rated for. However, maybe through the luck of the draw you get one drive that has one part of one NAND die go bad, or die early. The whole drive would be unable to function unless it has some kind of redundancy, like SF or the Intel 320 series.

Because it would take so long to get to 7700 PE cycles in a modern Win7/w TRIM environment under normal useage scenarios it would be more likely that something else happens along the way (20 years at 1PE cycle a day, 10 years at 2/day).

Quote:

---

Originally Posted by gordo

Also, for a given write load, doesn't increasing the size of the drive quickly make up for say the difference between 3k and 5k PE cycle NAND? In other words, if you have a massive write load application, just pick a bigger drive. Alternately, can't manufacturers just move to larger and larger SSDs to account for lower PE Counts associated with smaller and smaller smaller process NAND chips (all else being equal)?

---

Absolutely -- there is more flash to write to, and unlike endurance testing, the workload isn't infinite. So if your workload doesn't change, but you upgrade the current drive to a unit 2x the size, it will last much, much longer. It might take you 12 days to go through one PE cycle instead of 7.

Quote:

---

Originally Posted by gordo

Right, but once the NAND is beginning to reach its actual physical limits, assuming you have an excellent wear leveling algorithm, wouldn't one expect that the reallocations actually do start to happen almost all around the same time as each NAND cell reaches its limit?

---

You would think there is a brick wall, beyond which the NAND is just pushed too far. That's not the case though for the most part... all of the flash is different. Even if it does wear at the same rate, it will still not all die at the same time. If you were just putting the flash chips in a machine that did nothing but write and erase the flash, you might see most flash chips wear out at or around the same time.

Quote:

---

Originally Posted by Anvil

Kingston SSDNow 40GB (X25-V)

1000.01TB Host writes
Reallocated sectors : 05 46
Available Reserved Space : E8 99
POH 8953
MD5 OK

33.49MiB/s on avg (~132 hours)

---

Congratz :)

That took only a year :rofl:

Quote:

---

Originally Posted by Christopher

B.A.T. --

I'm excited -- I love those damn irritating MTRONs.


The erase count is literally the number of erases (I think it's in 1MB chunks). My 16GB MTRONS would decrease MWI around every 15 000 000 RAW. Unfortunately, because the drive is always doing GC and wear leveling the number is always increasing even if you're not writing to it. You could fill the drive to 100% look at before and after SMART shots, then erase the drive. The Samsung 51nm SLC is rated for 100K PE cycles, so 1 MWI should be 1000 PE cycles. 1000 * 32 768 MB = 32 768 000. Something like that, anyway.

The maximum raw value is 3 200 000 000 for the 32GB, should be 1 600 000 000 for the 16GB (but I have no way of verifying what the hell happens when you get that far).

Your drive is probably ~98.4 MWI if you want to think about it that way.

Writing a 1GB file to the PRO isn't going to tell you all that much. If you do it a couple times, it will be different each time.

I also think I have the .18R FW for your drive, but I would avoid flashing it like the plague. It's not like 4K RWs are going to skyrocket from 0.45MB/s to 0.50MB/s. But I get 46MB/s QD1 Random Reads with my PROs though. So that's nice, and you should be able to get a high avg speed.

---

Thanks for the info. I'll try some during the weekend.
btw here are the benchmark before I have done anything to the Mtron.
Attachment 127273

I'm going to SE it before I'll put it to the test.

--------------------------------------------

Plextor M3P 128GB Day 5

118,444.08 GiB
115.67 TiB

273.64 MB/s Average

119 Hours

Rellocated Event Count 0

--------------------------------------------

Samsung 830 256GB Day 75

1,782,813.16 GiB
1,741.03 TiB

305.46 MB/s Average
1765 Hours

7742 Wear Leveling Count
MWI 1

6/0 Erase/Program Fail
Used Reserved Block Count: 12/24572 sectors

--------------------------------------------

Quote:

---

Originally Posted by B.A.T

Mtron Pro 32GB SLC

Here are the smartvalues
Attachment 127266

The nand
Attachment 127267

The controller
Attachment 127268

And the spec
Link Link

I need some help to translate the raw value in total erase count.

---

Hi B.A.T, please find the file attached. it is the special tool for Mtron SSD. (Smartview)

http://www.mediafire.com/?34h0m6qk0nty25n

Thank you! I'll try it later today. :)

Quote:

---

Originally Posted by B.A.T

Thank you! I'll try it later today. :)

---

Ohh... what does it do? I wonder if it works with the Imation branded MTRONS.

Quote:

---

Originally Posted by neeyuese

Hi B.A.T, please find the file attached. it is the special tool for Mtron SSD. (Smartview)

http://www.mediafire.com/?34h0m6qk0nty25n

---

Sadly it doesn't recognize the Mtron. I don't know why.

Quote:

---

Originally Posted by Christopher

Ohh... what does it do? I wonder if it works with the Imation branded MTRONS.

---

It makes it possible to get more accurate info from the Mtron.

Attachment 127285

Todays update:

m4
981.1945 TiB
4131 hours
Avg speed 74.27 MiB/s.
AD gone from 52 to 48
P/E 16922.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=492726

Intel X25-M G1 80GB
673.67 TiB
23441 hours
Reallocated sectors : 104 to 106
Available Reserved space: 78
MWI= 114 to 103
MD5 =OK
40.61 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492725

Intel X25-E 64GB
174.04 TiB
529-30=499 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI= 98
MD5 =OK
100.62 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=492724

B.A.T.

Maybe it needs to be in IDE mode and not AHCI?

That is a good idea. I'll try that tomorrow. :up:

Quote:

---

Originally Posted by B.A.T

That is a good idea. I'll try that tomorrow. :up:

---

Hi B.A.T , maybe the firmware version on your Mtron drive is too old, both of my Mtron 3025 have the version 0.20r1 and working fine. Sadly the Mtron website down and very hard to find the correct version firmware now.

Some of mine have 17r and some have 18r, but the latest available for mine (they're Imation branded) is 18r.

Quote:

---

Originally Posted by Christopher

Some of mine have 17r and some have 18r, but the latest available for mine (they're Imation branded) is 18r.

---

Please find the 0.20r1 firmware links.

This firmware package support all Mtron SSD.

http://www.mediafire.com/?xw3ibgbp3bvbwuc

--------------------------------------------

Plextor M3P 128GB Day 6

140,407.73 GiB
137.11 TiB

273.07 MB/s Average

142 Hours

Rellocated Event Count 0
Attachment 127290

--------------------------------------------

Samsung 830 256GB Day 76

1,731,806,725.13 GiB
1,764.38 TiB

300.67 MB/s Average
1788 Hours

7846 Wear Leveling Count
MWI 1

6/0 Erase/Program Fail
Used Reserved Block Count: 12/24572 sectors

Quote:

---

Originally Posted by Christopher

B.A.T. --

I'm excited -- I love those damn irritating MTRONs.


The erase count is literally the number of erases (I think it's in 1MB chunks). My 16GB MTRONS would decrease MWI around every 15 000 000 RAW. Unfortunately, because the drive is always doing GC and wear leveling the number is always increasing even if you're not writing to it. You could fill the drive to 100% look at before and after SMART shots, then erase the drive. The Samsung 51nm SLC is rated for 100K PE cycles, so 1 MWI should be 1000 PE cycles. 1000 * 32 768 MB = 32 768 000. Something like that, anyway.

The maximum raw value is 3 200 000 000 for the 32GB, should be 1 600 000 000 for the 16GB (but I have no way of verifying what the hell happens when you get that far).

Your drive is probably ~98.4 MWI if you want to think about it that way.

Writing a 1GB file to the PRO isn't going to tell you all that much. If you do it a couple times, it will be different each time.

I also think I have the .18R FW for your drive, but I would avoid flashing it like the plague. It's not like 4K RWs are going to skyrocket from 0.45MB/s to 0.50MB/s. But I get 46MB/s QD1 Random Reads with my PROs though. So that's nice, and you should be able to get a high avg speed.

---

I think you are right about how it shows write.
1GB file increases the raw with 1200~1024 MiB
Filling the entire drive with 29.3 GiB increased the raw with 50000~48.8 GiB. That is a lot of writes in WA. It'll be exciting to see how long it will last.

I hope your MTRON lasts longer than the two I tried -- remember -- don't short it out! All I have to show for it is two dead MTRONs and a trail of tears.

How did you manage to do that? It's secure in the endurance rig so there should be no problems.

Quote:

---

Originally Posted by B.A.T

How did you manage to do that? It's secure in the endurance rig so there should be no problems.

---

Ha... I didn't say I was proud of the fact. And if I've proven anything, it's that no SSD is safe and secure when I'm around.,

Needless to say, the poor MTRON got shorted out because of something dumb I did. I had run it for a day or so in my other system before I put it in the endurance rig, and I managed to short it while moving it. It was a combination of rotten luck and bad decisions on my part.

The other MTRON died after some time, I rebooted the system and the MTRON had locked up. I tried flashing new firmware on it, but to no avail.

If I can track down 20r FW for the 16GB 7025, I'll give it another shot.

Do you know the difference between 17R and 20R?

Just a quick update. (busy with the new releases from MS for a few more days)

Attachment 127295

You may have noticed that the Samsung is Off the chart, it's currently at 1764TiB but as the other drives are way behind I've set a maximum of 1500TiB.
The chart in post#1 will be correct though.

Quote:

---

Originally Posted by Anvil

You may have noticed that the Samsung is Off the chart, it's currently at 1764TiB but as the other drives are way behind I've set a maximum of 1500TiB.
The chart in post#1 will be correct though.

---

Some thoughts for new charts which I would consider useful if possible: split the big chart on sections based on SSD capacity like <100GB SSDs, 100-200GB SSDs, etc. Also, maybe a more useful chart would be one in which total writes potential would be presented, normalized relative to a theoretical bigger SSD. In such a chart, a 40GB SSD with 1PB writes would be presented to have a theoretical write potential of 7.5PB relative to a 300GB model ( TotalSSDWrites * (300GB/SSDSize) ) . And for the dead ones, one extra information would be useful where it is possible to get it: average number of P/E cycles per day next to total writes. This should tell us if a slower write speed makes a difference or not.