SSD Write Endurance 25nm Vs 34nm

[B.A.T]

m4 update

245.2509 TiB
813hours
Avg speed 89.29 MiB/s.
AD gone from 228 to 213.
P/E 4290.
MD5 OK.
Still no reallocated sectors

[Vapor]

Just getting caught up, was AFK for the past few days. Good to see I didn't miss any drive failures

Compression testing on the SF-1200 ended early Saturday so that means I started on the endurance testing, and have a few observations from that:

1) Speed with an empty SF-1200 drive with the 46% setting was roughly ~61MiB/sec. With a drive with 34GiB taken up, it's down to ~56.2MiB/sec (24hr average). MD5 checks (every 10 loops) take up part of that, surely, but a 10% drop is bigger than I expected.

2) Wear range delta on the SF-1200 has gone down since endurance testing started (which is odd with static data, no?). It started at 8, was at 6 last night, and is now at 3.


Anyway, here's the strings of updates.

C300 64GB

156.745TiB host writes, 47MWI, 2651 raw wear, 2048/1 reallocations, MD5 OK
159.85TiB host writes, 46MWI, 2703 raw wear, 2048/1 reallocations, MD5 OK
163.42TiB host writes, 45MWI, 2763 raw wear, 2048/1 reallocations, MD5 OK
169.71TiB host writes, 43MWI, 2860 raw wear, 2048/1 reallocations, MD5 OK, 62.6MiB/sec (which is up by .7MiB/sec over when there was no SF-1200 onboard, odd).


SF-1200 nLTT 60GB

36.125TiB host writes, 19.125TiB NAND writes, 94 MWI, 6 wear range delta.
40.3125TiB host writes, 19.8438TiB NAND writes, 93 MWI, 7 wear range delta.
42.875TiB host writes, 21.719TiB NAND writes, 92 MWI, 8 wear range delta. Real endurance testing with static data, MD5 checks, and such started after this point.
46.813TiB host writes, 24.781TiB NAND writes, 91 MWI, 6 wear range delta, MD5 OK
48.125TiB host writes, 25.781TiB NAND writes, 90 MWI, 3 wear range delta, 56.2MiB/sec, MD5 OK.

[Anvil]

(been out of town for the weekend, test was off for about 36 hours)

220.19TB Host writes
Reallocated sectors : 6
MD5 OK

[bluestang]

M225->Vertex Turbo 64GB Update:

33.04 TiB
223 hours
MWI 74 (drops by 1 for every 50 raw wear)
1311 Raw Wear
40.52 MiB/s avg for the last 18.4 hours
MD5 OK

Also, C3 still at 2 and CE still at 235, same as last update.



EDIT: Found a new/old Indilinx Tool. Here is some info from it.

per-CE Count Info:


Bad Block List"


Erase Count List (too large to show, so here is summary):
BANK = Total (4096 BLK)
0 = 5348386
1 = 5446898
2 = 5408294
3 = 5380654
4 = 5444565
5 = 5428503
6 = 5492693
7 = 5431371

[johnw]

358.820 TiB, 974 hours, sa177: 1/1/29409, sa178: 68/68/324

368.289 TiB, 999 hours, sa177: 1/1/30182, sa178: 67/67/328

Average speed reported by Anvil's app has been steady at about 113MB/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 sa177 is average number of erase cycles for the flash, then the Samsung has just passed the rated cycles for a common type of Micron eMLC flash (30,000). Maybe the flash deterioration will accelerate soon.

[B.A.T]

m4 update:

252.4310 TiB
836hours
Avg speed 89.40 MiB/s.
AD gone from 213 to 209.
P/E 4416.
MD5 OK.
Still no reallocated sectors

[Vapor]

C300 Update

174.435TiB host writes, 41 MWI, 2950 raw wear, 2048/1 reallocations, MD5 OK


SF-1200 nLTT Update

52.625TiB host writes, 29.563TiB NAND writes, 88 MWI, 473 raw wear (equiv), MD5 OK

[Anvil]

222.75TB Host writes
Reallocated sectors : 6
MD5 OK

32.53MiB/s on avg (35 hours)

[bluestang]

M225->Vertex Turbo 64GB Update:

36.96 TiB
246 hours
MWI 71 (drops by 1 for every 50 raw wear)
1451 Raw Wear
43.93 MiB/s avg for the last 17 hours
MD5 OK

[johnw]

368.289 TiB, 999 hours, sa177: 1/1/30182, sa178: 67/67/328

377.470 TiB, 1024 hours, sa177: 1/1/30900, sa178: 66/66/344

Average speed reported by Anvil's app has been steady at about 113MB/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

[Ao1]

^ Incredible, especially at those speeds. By coincidence that is x100 the amount of data that I have written to my main SSD after a couple of years worth of use.

I wonder what the Sammy bases the MWI on? For the other SSD's it appears to be the theoretical minimum capability of NAND P/E cycles. There must be a good reason why the MWI in general appears to be way off for the other drives. Perhaps other thresholds are also considered, like the ability to retain static data over time once the MWI is getting close to depletion.

[johnw]

I think the Samsung does something similar with MWI to the other drives. It is just that the Samsung likely has WA of about 5, so it goes through the cycles a lot quicker than a drive with 1.1 WA.

[B.A.T]

m4 update:

259.9290 TiB
861hours
Avg speed 89.44 MiB/s.
AD gone from 209 to 205.
P/E 4547.
MD5 OK.
Still no reallocated sectors

[Vapor]

C300 Update

179.364TiB host writes, 40 MWI, 3034 raw wear, 2048/1 reallocations, 61.9MiB/sec, MD5 OK. ~11TiB more and it will have the longest lasting MWI so far


SF-1200 nLTT Update

57.125TiB host writes, 33.094TiB NAND writes, 87 MWI, raw wear 529.5 (equiv), wear range delta still at 3, 56.1MiB/sec, MD5 OK.


I think new charts tomorrow, next M225->Vertex Turbo update should move it past the Vertex 2 40GB in normalized writes and should be the last order change for awhile (have to recolor a lot of things in the bar charts every time the order changes). Samsung 470's reallocation line is...impressive

[bluestang]

M225->Vertex Turbo 64GB Update:

40.28 TiB
268 hours
MWI 69 (drops by 1 for every 50 raw wear)
1579 Raw Wear
34.55 MiB/s avg for the last 20 hours
MD5 OK

[Ao1]

As the V2 unthrottled drive has now written around the same amount of data before the V3 became throttled I thought I'd show a comparison. (I don't want to start a debate on the issue, but thought it was worth showing the comparison).

• The V2 dropped to MWI 87% whilst the V3 only dropped to 92% to write the same amount of data
• On avg the V2 dropped a MWI point per 2,420GB of data
• On avg the V3 dropped a MWI point per 3,752GB of data
• Reduction in writes between the V3 & V2 per MWI = 35%

The V2 = 32nm Hynix
The V3 = 25nm Intel

I doubt the V3 controller is that much better at reducing wear or that Intel's 25nm is that much better than the 32nm Hynix, so I'd guess that the MWI is linked in some way to LTT and the V3 was reporting the MWI "incorrectly". By this I'd guess more P/E cycles were depleted than indicated on the MWI, but LTT had not had a chance to correct the situation and bring P/E back in line with the MWI.

[bluestang]

Can someone explain what the attributes "CA-Total Count of Error bits from flash" and "CB-Total Count of Read Sectors with Corectable Bit Errors" are all about?

[deathman20]

m4 update:

259.9290 TiB
861hours
Avg speed 89.44 MiB/s.
AD gone from 209 to 205.
P/E 4547.
MD5 OK.
Still no reallocated sectors

Love these results there B.A.T Got the bigger brothers and new I wasn't in worry of the drives running out of room anytime soon but this just goes to show that the they can far exceed the 3k limit.

[Ao1]

Can someone explain what the attributes "CA-Total Count of Error bits from flash" and "CB-Total Count of Read Sectors with Corectable Bit Errors" are all about?

This white paper is a bit dated, but it explains why ECC is necessary and how it works.

http://www.imation.com/PageFiles/83/...hite-Paper.pdf

[bluestang]

This white paper is a bit dated, but it explains why ECC is necessary and how it works.

http://www.imation.com/PageFiles/83/...hite-Paper.pdf

Got it...Thanks!

[Anvil]

226.72TB Host writes
Reallocated sectors : 6
MD5 OK

34.28MiB/s on avg (33.45 hours)

[johnw]

377.470 TiB, 1024 hours, sa177: 1/1/30900, sa178: 66/66/344

386.728 TiB, 1049 hours, sa177: 1/1/31677, sa178: 65/65/350

Average speed reported by Anvil's app has been steady at about 113MB/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

[Anvil]

As the V2 unthrottled drive has now written around the same amount of data before the V3 became throttled I thought I'd show a comparison. (I don't want to start a debate on the issue, but thought it was worth showing the comparison).
...

Thanks for compiling the chart Ao1

I'm sure we'll be testing more of the SF based drives, when LTT is dropped or there are drives offered w/o LTT.

[B.A.T]

Love these results there B.A.T Got the bigger brothers and new I wasn't in worry of the drives running out of room anytime soon but this just goes to show that the they can far exceed the 3k limit.

And it just keeps going on. Just got to love'em

m4 update:

266.7679 TiB
883hours
Avg speed 89.39 MiB/s.
AD gone from 205 to 201.
P/E 4668.
MD5 OK.
Still no reallocated sectors

[SynbiosVyse]

Hello all

I am new here.

Running a Corsair Force 40 GB. The drive was completely virgin and is a slave drive obviously. Initial screenshots after NTFS format with 4096K allocation:



Min GiB free set to 36 GiB.

so far:

51.27 GiB written
0.26 hours
37.41 MB/s average

Where do you get P/E cycles? Please let me know if you need anything else.

P.S. I didn't realize the MD5 check was built-in to the utility until after i ran it, I generated my own checksums manually, but I will enable it if I ever stop the utility (stopping and resuming after would be okay right?)