SSD Write Endurance 25nm Vs 34nm

[Vapor]

Charts Updated

All bar charts are sorted by their respective equivalent of Writes So Far. SF-1200 MWI Exhaustion expectation is overly optimistic due to me still running compression tests (and 0-fill was redone after it went below 100MWI)....it will probably always be optimistic until MWI does deplete. SF-1200 observed WA is also optimistic, for the same reasons.

Host Writes So Far






Normalized Writes So Far
The SSDs are not all the same size, these charts normalize for available NAND capacity.






Write Days So Far
Not all SSDs write at the same speed, these charts factor out write speeds and look at endurance as a function of time.






Host Writes vs. NAND Writes and Write Amplication
Based on reported or calculated NAND cycles from wear SMART values divided by total writes.

[bluestang]

M225->Vertex Turbo 64GB Update:

81.16 TiB
387 hours
MWI 51 (drops by 1 for every 50 raw wear)
2451 Raw Wear
110.71 MB/s avg for the last 15.5 hours (on W7 x64)
MD5 OK



EDIT: And just think, my CD - Max PE Count Spec should be 10,000 for this NAND.

[SynbiosVyse]

05: 0
B1: 11
E7: 92%
E9: 16832
EA/F1: 29312

66.60 hours
28.5219 TiB
58.52 MB/s avg
MD5 Ok

[B.A.T]

m4 update:

311.0004 TiB
1026 hours
Avg speed 89.48 MiB/s.
AD gone from 179 to 175.
P/E 5447.
MD5 OK.
Still no reallocated sectors

[johnw]

433.397 TiB, 1175 hours, sa177: 1/1/35458, sa178: 55/55/452, 111.30 MB/s

442.500 TiB, 1200 hours, sa177: 1/1/36204, sa178: 51/51/496, 110.23 MB/s

The other unknown SMART attribute 235 is still at 99/99/2, just as it was when the SSD was fresh out of the box.

64GB Samsung 470

[devsk]

442.500 TiB, 1200 hours, sa177: 1/1/36204, sa178: 51/51/496, 110.23 MB/s

The other unknown SMART attribute 235 is still at 99/99/2, just as it was when the SSD was fresh out of the box.

64GB Samsung 470

If a drive with WA of 5 is able to write 0.5PB of data, is it fair to assume that the drive of the same size and NAND with WA of 1 will be able to write > 2PB of data? That would push these babies into enterprise land.

[B.A.T]

@vapor

I'm wonder about something. How do you calculate the WA in the charts?

[SynbiosVyse]

05: 0
B1: 12
E7: 92%
E9: 17792
EA/F1: 30464

72.15 hours
29.6435 TiB
58.54 MB/s avg
MD5 Ok

[Vapor]

@vapor

I'm wonder about something. How do you calculate the WA in the charts?

For the SF-1200s, I divide NAND writes by host writes reported by SMART attributes.

For the M225/C300/m4/Samsung470, I take ( reported raw wear ) / ( reported host writes (either SMART attribute or user reported) * 1024 / 64 ) (all drives are 64GiB NAND and 64GB available, so the 64 is applicable to all of them)

For the Intel X25-V with 5000 cycle NAND, I take ( 50 * (100-MWI) ) / ( user reported host writes * 1024 / 40 )

For the Intel 320 with 3000 cycle NAND, I take ( 30 * (100-MWI) ) / ( user reported host writes * 1024 / 40 ) (yes, it has 48GiB of NAND, but we don't know the parity scheme so only basing it on 40)


For instantaneous/recent WA, I just change the numerator and denominator to represent the change in the inputs from the most recent update(s).

All write amplification figures I list are just what WA appears to be from the data that's reported...if there's an error in the input, there's an error in the output.

[B.A.T]

Thank you! That fills up some of my knowledge gaps.

[One_Hertz]

314TiB. 58 reallocations. MD5 OK.

The available reserve space and the erase fail count both dropped down to 99 from 100. This happened either at 57 or 58 reallocated sectors.

[Vapor]

Extrapolated out that's 5600-5800, depending how they count...weird numbers

Of course, it is pretty inappropriate of me to extrapolate just on the smallest change possible

On a somewhat related topic, I wonder how big an Intel sector is this context....an LBA sector, a page, a block, or some other unit?

[Computurd]

@Anvil or Vapor-
could you guys update charts on post #1? i have been linking this quite a bit and it makes it easier for others to see results on first post

[bluestang]

M225->Vertex Turbo 64GB Update:

87.51 TiB
402 hours
MWI 49 (drops by 1 for every 50 raw wear)
2571 Raw Wear
110.75 MB/s avg for the last 16.7 hours (on W7 x64)
MD5 OK

EDIT: C4 Erase Failure Block Count went from 0 to 1. (missed that, sorry)

[johnw]

442.500 TiB, 1200 hours, sa177: 1/1/36204, sa178: 51/51/496, 110.23 MB/s

450.872 TiB, 1223 hours, sa177: 1/1/36889, sa178: 43/43/574, 108.21 MB/s

The other unknown SMART attribute 235 is still at 99/99/2, just as it was when the SSD was fresh out of the box.

64GB Samsung 470

At this rate (sa178), may only have a few days left...
It is slowing down a little, too. Maybe because of less reserved space.

[Vapor]

C300 Update

219TiB host writes, 26MWI, 3702 raw wear, 2048/1 reallocations, 62.5MiB/sec, MD5 OK


SF-1200 nLTT Update

92.625TiB host writes, 60.719TiB NAND writes, 72 MWI, 971.5 raw wear (equiv), 56.35MiB/sec, MD5 OK

@Anvil or Vapor-
could you guys update charts on post #1? i have been linking this quite a bit and it makes it easier for others to see results on first post

Thanks for the reminder, will get to it after this post

450.872 TiB, 1223 hours, sa177: 1/1/36889, sa178: 43/43/574, 108.21 MB/s

The other unknown SMART attribute 235 is still at 99/99/2, just as it was when the SSD was fresh out of the box.

64GB Samsung 470

At this rate (sa178), may only have a few days left...
It is slowing down a little, too. Maybe because of less reserved space.

Also of interest, your overall WA has decreased when sa178 started increasing. It was a very steady 5.14x before sa178 went on the move and now it's down to 5.11x overall. Since sa178 started moving, recent WA has been mostly steady at 5.075x.

Yes, pretty small change, but the considering the previous stability, the suddenness, and the timing of this change I find it very interesting.

Also, the reallocation line took a very noticeable turn upward...I agree that it may only have a few days left.

[B.A.T]

m4 update:

319.0516 TiB
1052 hours
Avg speed 89.49 MiB/s.
AD gone from 175 to 170.
P/E 5589.
MD5 OK.
Still no reallocated sectors

[Hopalong X]

One_Hertz

FYI

http://communities.intel.com/thread/24205

Intel has the firmware update available if interested. It took me about 10 minutes total.
Mike

[johnw]

450.872 TiB, 1223 hours, sa177: 1/1/36889, sa178: 43/43/574, 108.21 MB/s

454.959 TiB, 1234 hours, sa177: 1/1/37220, sa178: 39/39/620, 108.10 MB/s

The other unknown SMART attribute 235 is still at 99/99/2, just as it was when the SSD was fresh out of the box.

64GB Samsung 470

Two updates today.

[devsk]

454.959 TiB, 1234 hours, sa177: 1/1/37220, sa178: 39/39/620, 108.10 MB/s

The other unknown SMART attribute 235 is still at 99/99/2, just as it was when the SSD was fresh out of the box.

64GB Samsung 470

Two updates today.

The question is if it will break the 500TiB barrier or break before it?

[bluestang]

M225->Vertex Turbo 64GB Update:

93.58 TiB
416.5 hours
MWI 47 (drops by 1 for every 50 raw wear)
2687 Raw Wear
110.92 MB/s avg for the last 16 hours (on W7 x64)
MD5 OK
C4-Erase Failure Block Count(Realloc Sectors) at 1 (BANK 6, Block 2406, Erased 2552 times)

[SynbiosVyse]

05: 0
B1: 17
E7: 87%
E9: 24576
EA/F1: 38912
F2: 64

112.97 hours
37.8914 TiB
58.65 MB/s avg
MD5 Ok

[johnw]

The question is if it will break the 500TiB barrier or break before it?

Such questions are rather arbitrary. It has already passed 500TB, for example.

[devsk]

Such questions are rather arbitrary. It has already passed 500TB, for example.

What I meant was that death counter (we don't know for sure if it is so but still) is going down fast, almost 1 per TiB. So, its really a stretch if it makes it past 500TiB.

[johnw]

454.959 TiB, 1234 hours, sa177: 1/1/37220, sa178: 39/39/620, 108.10 MB/s

460.056 TiB, 1249 hours, sa177: 1/1/37631, sa178: 32/32/684, 107.43 MB/s

The other unknown SMART attribute 235 is still at 99/99/2, just as it was when the SSD was fresh out of the box.

64GB Samsung 470