SSD Write Endurance 25nm Vs 34nm

[Vapor]

The more I think about it, the more it sounds like sizable chunk of data being unaccounted for in the early lifetime of the drive. If there were 100GB unaccounted for in the beginning, its impact as a percentage would get smaller and smaller as writes increased, basically asymptotic behavior. I haven't done any math to see what size that would be, but it might match up nicely with the attempts of getting the right amount of static data on the drive (or even the 39GB itself).

[B.A.T]

That might be it. First I ran 1 run of Anvils benchmark, ATTO and AS SSD. Then I copied the static of 39,3GiB and started the endurance test. I don't know how much AS SSD and ATTO writes but Anvils app is supposed to keep the write to an minimum.

[bulanula]

Very good to see the 300 TB barrier being broken so quickly by the Samsung !

[Vapor]

C300 Update

139.04TiB, 53 MWI, 2350 raw wear, reallocations still at 2048/1, MD5 OK


SF-1200 nLTT Update

13.563TiB Host writes, 7.53TiB NAND writes, 99 MWI, 120.5 raw wear, wear range delta 1.

[Ao1]

Interesting.

The V2 (34nm) took 11.60TiB before the MWI dropped to 99%. Out of that 11.6TiB approx 4TB was 0fill.
The V3 (25nm) took 11,078 GiB (NAND writes) before the MWI dropped to 99%.

[Anvil]

207TB Host writes
Reallocated sectors 6
MD5 OK

34.22MiB/s on avg for the last 21 hours.

[bluestang]

M225->Vertex Turbo 64GB Update:

14.14TiB, MWI 89, 557 Raw Wear, 49.70MiB/s for the last 21.25 hours (<-stopped, ran wiper, then restarted)
No MD5 Testing yet.

Also, C3 from 1 to 2 and CE from 214 to 235.



EDIT: When should I start MD5 Testing?

[Ao1]

Whoa, that is a savage reduction in the MWI considering the drive has 5K P/E. Personally I would not bother with MD5 Testing until the MWI gets very low or unless C3/ CA/ CB start changing significantly.

Looks like the health status is established by D0 (avg erase count) / PE specification count.

[bluestang]

I now alot of people notice their drive life drop by 50% or more when they went from Indilinx FW 1916 to FW 2030.
It changed the P/E count from 10k to 5k to cover other NAND I believe.

I think we're good for 10k P/E myself

[Ao1]

Did you post which type of NAND the SSD is using? (Product ID) If not do you know? If you could let me know I can try to find the product literature. Then we can be sure about the P/E spec.

[bluestang]

NAND is Samsung K9LBG08U0M-PCB0

EDIT: Not sure if this helps ya... http://www.datasheetarchive.com/inde...DSA0038979.pdf

[Ao1]

Looks like it is 51nm and at some stage the P/E cycle specification was changed from 5k down to TBD

[B.A.T]

m4 update:
Getting close to Anvil now
The rigg was down 2 hours last night due to some maintenance.

206.0306 TiB
684hours
Avg speed 91.69 MiB/s.
AD gone from 240 to 236.
P/E 3601.
MD5 OK.
Still no reallocated sectors

[bluestang]

Looks like it is 51nm and at some stage the P/E cycle specification was changed from 5k down to TBD

I have these notes for some reason in my M255 junk. Don't know where they came from though:

revision history

endurance

April 12th 2006 : 10,000 times

Dec. 22th 2006 : 10,000 times -> 5,000 times

Jan. 12th 2007 : 5,000 times -> TBD

[Vapor]

C300 Update

142.01TiB, 52MWI, 2401 raw wear, 2048/1 reallocations, MD5 OK


SF-1200 nLLT 60GB Update

17.188TiB host writes, 10.063TiB NAND writes, 98 MWI, 161 raw wear, wear range delta of 3. Still doing compression tests so still no static data or MD5 testing.

[johnw]

302.868 TiB, 826 hours, sa177: 1/1/24873, sa178: 71/71/290

312.510 TiB, 851 hours, sa177: 1/1/25623, sa178: 71/71/292

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

sa178 raw increase of 2 this time

[B.A.T]

Just for fun.


Nice result after 207 TiB is written

[bluestang]

^^Makes me feel good about buying 2 for my RAID0

[Anvil]

@B.A.T
Looks like it's brand new

--
209.85TB Host writes
Reallocated sectors : 6
MD5 OK

36.47MiB/s on avg (12 hours)

[One_Hertz]

271TiB. 39 reallocated sectors. The value which I believe to be the wear indicator is 135.

[bulanula]

Please try and see if you can get TRIM working on the Indilinx drive otherwise this test is not really life like.

[bluestang]

Please try and see if you can get TRIM working on the Indilinx drive otherwise this test is not really life like.

Sure it is, plenty of people run RAID --- No TRIM.
And yes, some people still run XP and Vista -- No TRIM.

[B.A.T]

^^Makes me feel good about buying 2 for my RAID0

I think 2 in raid 0 is a killer combo. m4 is looking very impressive and they are cheap

@B.A.T
Looks like it's brand new

Yeah. It's not much difference from my first run with AS SSD.

[bluestang]

I think 2 in raid 0 is a killer combo. m4 is looking very impressive and they are cheap

Picked up to for $99 each

I'll try and post some benches later tonight in the SSD Roundup thread.

[Anvil]

Please try and see if you can get TRIM working on the Indilinx drive otherwise this test is not really life like.

Of course it is life like, Intel recommends running Intel SSD Toolbox once every week, which would equal every 10-140GB depending on your usage pattern.
TRIM will not clean all "deleted" data even if you are running an OS supporting TRIM. (this is why it is recommended running the toolbox)

Not sure how many GB is written between each run of "wiper" but it is surely much more than the recommended 10-140GB, a lot more , an average of 40MiB/s equals 1 week of writes written in just 1 hour.
So if he cleans the drive once per day it would equal (a minimum) of 24weeks of writes, so, he can in fact run "wiper" once every hour and still be within the norm.