SSD Write Endurance 25nm Vs 34nm

Todays update. Nice to have 24h without problems :)
Kingston V+100
325.6350 TiB
1778 hours
Avg speed 25.05 MiB/s
AD still 1.
168= 1 (SATA PHY Error Count)
P/E?
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=474842http://www.diskusjon.no/index.php?ap...tach_id=474839

Intel X25-M G1 80GB
212,6894 TiB
20087 hours
Reallocated sectors : 00
MWI=143 to 142
MD5 =OK
50.69 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=474841http://www.diskusjon.no/index.php?ap...tach_id=474838

m4
192.9329 TiB
707 hours
Avg speed 80.03 MiB/s.
AD gone from 248 to 243.
P/E 3392.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=474843http://www.diskusjon.no/index.php?ap...tach_id=474840

While I wait for the 830 to finish it's idle session, I'm reflecting on the performance of the 40GB Intels. In a way, the fact that they're continuing with no sign of slowing is pretty damn impressive. The 320 should hit 700TB before too long, which is just plain awesome for a 40GB drive. I still think there is something to the slow and steady approach.

So far the 830 is coping quite well with the 4K random work load. 177 does not update properly unless you power cycle, but at least the LBA count seems to be working OK now. Everything else seems to update as well, so it’s just 177.

http://img213.imageshack.us/img213/1...powercycle.png

http://img38.imageshack.us/img38/884...powercycle.png

64GiB * P/E Cycles (115) = 7,360
Actual writes = 868
WA = 8.47 (Ouch)

Quote:

---

Originally Posted by Ao1

64GiB * P/E Cycles (115) = 7,360
Actual writes = 868
WA = 8.47 (Ouch)

---

I am surprised it is not higher since you are doing nothing but full-span 4KiB random writes.

By the way, did you verify that 512 * LBA count is equal to the bytes written according to ASU?

^ Yes. In post # 3189 the total LBA count was 1433682636. (Just before starting the 4K workload). In post #3194 the LBA count was 1819470188. The difference = 385787552 or 184 GiB.

Anvils app is showing 126,454.69 MiB plus 59.51 GiB for the test file = 183 GiB.


EDIT:

64GiB * P/E Cycles (189) = 12,096
Actual writes = 1,056
WA = 11.45
MWI (?) 94

My 830's Sector written count is about 900GB more than ASU, but most of that is writes from other sources over the past month. I believe it is pretty accurate.

Quote:

---

Originally Posted by Ao1

64GiB * P/E Cycles (189) = 12,096
Actual writes = 1,056
WA = 11.45
MWI (?) 94

---

Aha, WA going up. I wonder what it will stabilize at. It would be interesting to try this:

1) power-cycle the SSD and then note the raw values of attributes 177 and 241, call them r177a and r241a

2) run ASU endurance writes for a while, a day or two, note the ASU bytes written at the beginning and end of the period

3) power-cycle the SSD and check attributes 177 and 241 again, call it r177b and r241b

4) verify that the ASU bytes written = 512 x (r241b - r241a)

5) compute the WA = 64 x 1024^3 x (r177b - r177a) / ( 512 x ( r241b - r241a ) )

By the way, what QD does ASU Enterprise endurance benchmark use for its full-span 4KiB random writes? I suppose QD does not matter much for the 4KiB random write speed on the Samsung 830, but for some SSDs (like the m4 or Performance Pro), the write speed increases quite a bit with higher QD.

Quote:

---

Originally Posted by johnw

I am surprised it is not higher since you are doing nothing but full-span 4KiB random writes.

---

If I count only the 4K writes the WA is currently coming out at 29.47 (What I reported before included all write activity)

From the graph below the temp of the SSD has jumped by around 20 oC once I started with the 4K workload. The red lines coincide exactly with power off cycles.

http://img853.imageshack.us/img853/3522/tempchange.png

EDIT, the SSD is noticeably warmer to touch. I’d say that the temp readings are quite accurate.

Quote:

---

Originally Posted by johnw

By the way, what QD does ASU Enterprise endurance benchmark use for its full-span 4KiB random writes? I suppose QD does not matter much for the 4KiB random write speed on the Samsung 830, but for some SSDs (like the m4 or Performance Pro), the write speed increases quite a bit with higher QD.

---

According to the resource monitor the QD is 1.

Quote:

---

Originally Posted by Ao1

If I count only the 4K writes the WA is currently coming out at 29.47 (What I reported before included all write activity)

---

That is more like the WA I would expect to see for full-span 4KiB random write.

So I'm entertaining ideas on what to do with this:

https://www.box.com/shared/static/8x...24sc15kuax.jpg

It's an MTRON PRO 7000 (msp7035). It is faster than I thought, but not by much. It's a 3.5" 16GB drive, and it's pretty old school.

But it's is brand new, never been opened.

EDIT
I ran ASU for a while, and after 70GB of writes, the one SMART attribute's RAW value went from 324393 to 453601, and was able to do about 51MB/s.

I'm going to have to take the drive apart as I'm curious to see whether the PCB inside is 3.5" or 2.5" inches among other things. It just seems ridiculous to put 16GB of NAND inside a 3.5" enclosure.

Samsung 830 64GB Update, Day 33
FW:CXM01B1Q

GiB written:
205213.42

Avg MB/s
86.87

PE Cycles
13017, up from 12503 yesterday

Reallocated Sectors
40960
20 Blocks, up from 18

796 Hours

https://www.box.com/shared/static/cz...js6gdy6jqv.png
https://www.box.com/shared/static/tb...3ntq5k5q65.png
https://www.box.com/shared/static/96...qnkpquk5qa.jpg

The 7 hours of idle time combined with halving the static data down to 18.5GB seems to have increased speed by 20MB/s. I'm not sure how long it will last.

Todays update.
Kingston V+100
327.5644 TiB
1801 hours
Avg speed 25.02MiB/s
AD still 1.
168= 1 (SATA PHY Error Count)
P/E?
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=474991http://www.diskusjon.no/index.php?ap...tach_id=474988

Intel X25-M G1 80GB
216,5665 TiB
20109hours
Reallocated sectors : 00
MWI=142 to 141
MD5 =OK
50.41 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=474990http://www.diskusjon.no/index.php?ap...tach_id=474987

m4
199.1485 TiB
730 hours
Avg speed 80.31MiB/s.
AD gone from 243 to 240.
P/E 3502.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=474992http://www.diskusjon.no/index.php?ap...tach_id=474989

MTRON claims a 32GB drive can write 50GB a day for 140 years, so assume 50GB a day for 70 years with the 16GB 7000.

That would equal 1,277,500GB, which is realistic if the NAND is rated for 100,000PE cycles. If the MTRON could maintain 3500GB per day in ASU, I could hit 1,277,500GB in only 365 days. 41MB/s avg would be 3500GB a day so that seems reasonable.

Of course, if the NAND is 200,000PE rated and the drive has decent WA/WL, then all bets are off. It could be more like 3 years. I only ran a couple of loops with no static data and 3GB min free space, so I can't say whether the lack of TRIM is going to wreck avg speed or not. But it could be feasible to test the drive in a reasonable time span -- maybe. The lack of SMART data is irritating (ONE attribute? Why bother?), and I don't even know how the one attribute works.

The 3.5" chassis is quite nice. It weighs almost as much as a single platter 3.5" HDD.

Quote:

---

Originally Posted by Ao1

According to the resource monitor the QD is 1.

---

Have you tried "Performance Monitor" of Windows 7? Sometimes I get strange readings from "Resource Monitor"...

Average WA
60GiB (LBA) * P/E Cycles (308) = 18,480
Actual writes = 1,398
WA = 13.31

4K Random only WA
60GiB (LBA) * P/E Cycles (268) = 16,080
Actual writes = 666
WA = 24.14

MWI: 91
Avg write speed = 4.31MiB/s

In the Toolbox/ System Information it states that the MAX LBA is 125045424, so I am now using 60GiB rather than 64GiB.

177 is still only updating after a power cycle.

Quote:

---

Originally Posted by minpayne

Have you tried "Performance Monitor" of Windows 7? Sometimes I get strange readings from "Resource Monitor"...

---

Yes and it reports the same.

Quote:

---

Originally Posted by Christopher

The 7 hours of idle time combined with halving the static data down to 18.5GB seems to have increased speed by 20MB/s. I'm not sure how long it will last.

---

Christopher, during the idle time did the SMART atribute 177 update?

Kingston SSDNow 40GB (X25-V)

615.24TB Host writes
Reallocated sectors : 05 21
Available Reserved Space : E8 99
POH 5560
MD5 OK

33.38MiB/s on avg (~111 hours)

--

Corsair Force 3 120GB

01 89/50 (Raw read error rate)
05 2 (Retired Block count)
B1 70 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 662250 (Raw writes) ->647TiB
F1 881407 (Host writes) ->861TiB

MD5 OK

106.81MiB/s on avg (~159 hours)

power on hours : 2533

WRD is all time high as far as I can see. (since the retention test it has been increasing steadily)

--

http://www.ssdaddict.com/ss/Endurance_cr_20120108.png

http://www.ssdaddict.com/ss/Enduranc...y_20120108.png

Anvil, my opinion is that the "true" WA of Christopher's Samsung 830 64 GiB was around 3.93 under Endurance-testing of ASU, and the estimated "MWI exhausted" was supposed to be around 44.4 TiB if the P/E spec was 3000.

I'm also confused by your last figure, the "P/E Cycle summary". I suppose it's not the true P/E count, but instead, the P/E count divided by WA?

By the way, we can't wait to get the beta11 with the Enterprise-test :D

The P/E Cycle summary is Based on

Host Writes / Capacity

I'll explain a bit more later, I haven't found a better title for the chart,yet.

Then that's the same as what I thought:

Host Writes / Capacity == P/E Cycles / WA

I would call it "Reduced P/E Cycles after WA" :p:

Quote:

---

Originally Posted by Ao1

Christopher, during the idle time did the SMART atribute 177 update?

---

Negative. Not even by one as it did in the beginning.

Thanks for confirming that Christopher.

I just used hIOmon to see if TRIM operations had time to execute. TRIM with the normal ASU client workload works OK, in fact TRIM operations are lightning fast compared to SF. It took only 8.79ms for a 50GB file delete. SF = 20 seconds plus)
With the ASU enterprise workload however it seems that TRIM operations don’t occur and I'd guess that would be the same for any SSD with that workload.

Samsung 830 64GB Update, Day 34
FW:CXM01B1Q

GiB written:
211183.25

Avg MB/s
70.25

PE Cycles
13321, up from 13017 yesterday

Reallocated Sectors
40960
20 Blocks, up from 18

820 Hours

https://www.box.com/shared/static/uj...imxo296eg9.png
https://www.box.com/shared/static/8b...3h8zyq038p.png

Double post