Okay both are still 0 for me. I will start reporting them once I see them go up.
Printable View
C300 Update
204.177TiB host writes, 31 MWI, 3452 raw wear, 2048/1 reallocations, MD5 OK, 62.5MiB/sec
SF-1200 nLTT Update
79.69TiB host writes, 50.69TiB NAND writes, 77 MWI, 811 raw wear (equiv), wear range delta 3, MD5 OK, 56.3MiB/sec
Correct. What I referred as a "cycle" is the idea that you cannot have a program unless the page is part of a block which was erased. Because there is normally no program operation during a SE, there will be no "cycle" and no write counting. Now what would be interesting is to have a counter for both block erases and page writes, because this would give us a 100% accurate write amplification number. Unfortunately, I saw no SSD to count both parameters.
M225->Vertex Turbo 64GB Update:
75.24 TiB
373 hours
MWI 54 (drops by 1 for every 50 raw wear)
2337 Raw Wear
114.26 MB/s avg for the last 66.5 hours (on W7 x64)
MD5 OK
Attachment 118996
433.397 TiB, 1175 hours, sa177: 1/1/35458, sa178: 55/55/452, 111.30 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
Yesterday I noticed that the Avg MB/s field had been creeping down very slowly, in the 0.01 digit each day. It was still 113.13, but it seemed like the speed was decreasing. I think that ASU was averaging the speed from the last time the program was first started, which was many days ago. So after yesterday's data, I restarted ASU so that the average speed reported would only be for the last day. So today it read 111.30 MB/s. I'll keep restarting ASU after each day's data so that the average is only for the last day, and reporting the speed.
Very interesting on the last two updates.
M225->Vertex Turbo 64GB's recent WA is still shrinking. It was 1.89x for the chunk of initial TRIM-enabled test, 1.228x for the 2nd chunk, and was 1.14x for the most recent chunk. It makes sense that net WA reduces as the proportion of low-WA writes increases, but the actual recent/instantaneous WA is still shrinking too :eek: :yepp:
I don't want to get too spammy with the charts (full chart update later today, I think), but the Samsung 470's reallocated sector count slope is starting to turn upward even with the logarithmic scale....death march has turned into a jog.
m4 update:
Been away for the weekend but my m4 has been working like a busy bee. :D
304.3266 TiB
1004 hours
Avg speed 89.46 MiB/s.
AD gone from 193 to 179.
P/E 5329.
MD5 OK.
Still no reallocated sectors
Attachment 119005
05: 0
B1: 9
E7: 94%
E9: 13952
EA/F1: 25728
49.32 hours
25.0284 TiB
58.38 MB/s avg
MD5 Ok
C300 Update
210.195TiB host writes, 29 MWI, 3553 raw wear indicator, 2048/1 reallocations, 62.45MiB/sec, MD5 OK
SF-1200 nLTT Update
84.938TiB host writes, 54.75TiB NAND writes, 75 MWI, 876 raw wear (equiv), 56.3MiB/sec, MD5 OK
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
Attachment 119011
Attachment 119012
Normalized Writes So Far
The SSDs are not all the same size, these charts normalize for available NAND capacity.
Attachment 119013
Attachment 119014
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.
Attachment 119015
Attachment 119016
Host Writes vs. NAND Writes and Write Amplication
Based on reported or calculated NAND cycles from wear SMART values divided by total writes.
Attachment 119017
Attachment 119018
Attachment 119019
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
Attachment 119025
EDIT: And just think, my CD - Max PE Count Spec should be 10,000 for this NAND.
05: 0
B1: 11
E7: 92%
E9: 16832
EA/F1: 29312
66.60 hours
28.5219 TiB
58.52 MB/s avg
MD5 Ok
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
Attachment 119035
@vapor
I'm wonder about something. How do you calculate the WA in the charts?
05: 0
B1: 12
E7: 92%
E9: 17792
EA/F1: 30464
72.15 hours
29.6435 TiB
58.54 MB/s avg
MD5 Ok
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.
Thank you! That fills up some of my knowledge gaps. :)
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.
Extrapolated out that's 5600-5800, depending how they count...weird numbers :p:
Of course, it is pretty inappropriate of me to extrapolate just on the smallest change possible :lol:
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?
@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 :)
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)
Attachment 119048
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.
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
Thanks for the reminder, will get to it after this post :)
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.