SSD Write Endurance 25nm Vs 34nm

Todays update:

m4
895.2967 TiB
3785 hours
Avg speed 74.44 MiB/s.
AD gone from 102 to 98.
P/E 15435.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=490951

Intel X25-M G1 80GB
622.76 TiB
23097 hours
Reallocated sectors : 156 to 157
Available Reserved space: 90
MWI=124
MD5 =OK
42.03 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490955

Intel X25-E 64GB
54.54 TiB
184-30=154 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.46 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=490953

Still deciding if I should throw a sandisk extreme 120gig into the mix .... they are quite inexpensive, and would be interesting to test the 24nm NAND.

That is an interesting drive!
I was considering that one but the shop that sells them extremely cheap doesn't sell to businesses. (I won't get a tax refund)

Looks like the Intel 330 could be it!
Plextors are still too expensive here, the M3P (~$260) is more or less 2x the price of a SanDisk Extreme and about $50 more than most other drives like the Intel 520 (~$210), almost $100 more than an m4 ($165).

I happen to not be using my 128GB M3P at the moment... It has host writes and MWI now...

Actually, I'm not using most of my drives. But I really want to test the M3P!

They're $210 here at the moment, but the 128GB 830 is only $109 this weekend, so if I were making a buying decision, I'd take the 830. Since I already own the M3P, the choice is clear.

Can anyone think of a good reason not to test it?

I won't be entering a M3P so feel free :)

Agility 4s are starting to surface, wonder whats up with that vs Vertex 4?

Not much info on the Agility 4, this is all I have found on the 128GB (Agility 4 Max R/W 400 MB/ 300 MB sec)

Samsung 830 256GB Day 61

1,452,304.28GiB
1,418.26 TiB

297.51 MB/s Average
1438 Hours

6311 Wear Leveling Count
MWI 1

5/0 Erase/Program Fail
Used Reserved Block Count: 10/20480 sectors

Intel 520 60GB - Day 86

Drive hours: 2,011
ASU GiB written: 637,689.27 GiB (622.74 TiB)
Avg MB/s: 95.42 MB/s
MD5: OK

Host GB written (F1): 642,255.88 GiB (627.20 TiB, 20552188 raw)
NAND writes (F9): 454,676 GiB (444.02 TiB)

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

Vertex 4 128GB - Day 33

Drive hours: 801 (556 + 245)
ASU GiB written: 345,315.27 GiB (337.22 TiB)
Avg MB/s: 123.96 MB/s
MD5: OK

Sector GB written (E8): 348,370.44 GiB (340.21 TiB, 486156078177 + 244429690650 raw)
Reallocated sectors (05): 4
Raw Read Error Rate (01): 6
Remaining Life (E9): 44 (74 current - 30)

Hmm, 3 more bad blocks in the last 48h. Hopefully this vertex 4 isn't following the same path as the octane before it.

Might not be a good idea to flash to 1.4 as SMART values are reset.

The next 48hours should tell if there is something going on, there shouldn't be that much in common with the Octane except for the casing.

Quote:

---

Originally Posted by Anvil

The next 48hours should tell if there is something going on, there shouldn't be that much in common with the Octane except for the casing.

---

Except for the same people writing the firmware!

Todays update:

m4
901.3566 TiB
3809 hours
Avg speed 74.39 MiB/s.
AD gone from 98 to 95.
P/E 15538.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=491341

Intel X25-M G1 80GB
626.27 TiB
23121hours
Reallocated sectors : 157 to 158
Available Reserved space: 90
MWI=124
MD5 =OK
42.19 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=491343

Intel X25-E 64GB
62.85 TiB
208-30=178 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.36 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=491345

It's like looking at grass grow but now it's only 2 weeks left before 1 PiB is broken :)

I'm also considering to throw in a C300 128GB since Vapor never returned here. Got a couple of them laying around and it could be interesting to compare with the m4.

@canthearu

I forgot about that one :)

@B.A.T

Looking good, not much variation in speed on the E.

A C300 would be great!
Can you manage all the drives on one rig :)

I'll order something by Monday!

I got 8 SATA ports on that motherboard so no problem. Just need to manage some power and sata cables behind the hdd cage.

Next time I'll remove the Torqx 2 from the chart.

Attachment 126897

--

Kingston SSDNow 40GB (X25-V)

966.06TB Host writes
Reallocated sectors : 05 43
Available Reserved Space : E8 99
POH 8659
MD5 OK

37.93MiB/s on avg (~6 hours)

@canthearu

Is there anything you'd like to add or adjust on the Torqx 2 summary?
(the list is updated in post #1)

@Anvil

You need to change model name to Torqx 2.

Also, the Torqx 2 was showing a lot of write failures in the windows log and extremely unresponsive at the end.

I'm running now 1155 Z77 board now if that makes a difference if you want to put it in.

I'll fix it.

When did you make the change to Z77?

I think I'm going to skip IB, a bit surprised that it's hotter than SB, maybe they can get it fixed in some revision.

About when I got the vertex 4 (probably 1 week after) I got the Z77 board along with an i3-2120

IB Board: Maybe
IB CPU: Probably Not

That is a good point, chipset USB3 and probably Thunderbolt on some boards.
(must check)

A bit random, but somehow I think this thread will be running for a very long time.

The vast bulk of the NAND market is for mobile devices. Performance for mobile devices is more dependent on larger block performance, hence continuing increases in page sizes as NAND geometry shrinks. This of course is not helpful for SSD’s, so as page sizes increase and NAND geometry shrinks SSD controllers become more complex. Geometry shrinks get progressively harder, but the limit is still not known. The pace of geometry shrinks (and the resulting changes in NAND composition) is really the technology driver for SSD’s. The controllers have to keep up. In this context it’s easy to see that controllers have a very limited life span and consequently I think this is why the controller market has consolidated.

The very structure of NAND may change altogether.

Attachment 126930

NAND die shrinks

Attachment 126932

Attachment 126933

Bring on the 3D ReRAM :)

Attachment 126934

Samsung 830 256GB Day 63

1,495,909.52GiB
1,640.85 TiB

292.17 MB/s Average
1415 Hours

6500 Wear Leveling Count
MWI 1

5/0 Erase/Program Fail
Used Reserved Block Count: 10/20480 sectors

Todays update:

m4
907.8599 TiB
3834 hours
Avg speed 74.36 MiB/s.
AD gone from 95 to 91.
P/E 15648.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=491478

Intel X25-M G1 80GB
630.06 TiB
23146 hours
Reallocated sectors : 158
Available Reserved space: 90
MWI=124
MD5 =OK
42.33 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=491482

Intel X25-E 64GB
71.77 TiB
233-30=203 hours
Reallocated sectors : 0
Available Reserved space: 100
MWI=99
MD5 =OK
101.31 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=491480

With this speed on the E it'll write 3.6 PiB the next year :shocked:

Quote:

---

Originally Posted by B.A.T

With this speed on the E it'll write 3.6 PiB the next year :shocked:

---

I'm not 100% convinced that you can actually wear out the E's 50nm SLC unless you're doing full span high QD random writes... who knows?:shrug:

First I need to find out how long it takes to mwi=1%. Then it's possible to do some predictions.

You could reset the timed workload media workload and it would be possible to tell quite quickly how long it will take for the MWI to expire.

What I found with the 830 is that 4k RW did not wear out the drive any quicker because the write speeds were so slow in comparison to the normal ASU workload. I would suspect that 4K RW at QD 34 would help reduce wear whilst maintaining a higher write speed, but it would be interesting to experiment and monitor using the workload timer. Lol, I paid £600 each for 2 of the X25-E’s when they very first came out and now I see Christopher picks one up for peanuts. I’ll keep my eye out for one.