Normally that's not an issue, the issue in this case is the drive that's not consistent.Quote:
Originally Posted by Christopher
(CDM could have used the average but that would not be representative in this case either)
Printable View
Normally that's not an issue, the issue in this case is the drive that's not consistent.Quote:
Originally Posted by Christopher
(CDM could have used the average but that would not be representative in this case either)
So I'm looking for suggestions for a new drive to test. I have acquired several drives recently that could be considered good test candidates to one degree or another, but I thought I'd put the question out there.
Any suggestions?
Todays update.
Kingston V+100
http://www.diskusjon.no/index.php?ap...tach_id=475187
This one has dropped out again.
Intel X25-M G1 80GB
224,4992 TiB
20157 hours
Reallocated sectors : 00
MWI=140 to 149
MD5 =OK
49.15 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=475185http://www.diskusjon.no/index.php?ap...tach_id=475184
m4
212.3534 TiB
778 hours
Avg speed 80.54 MiB/s.
AD gone from 236 to 232.
P/E 3736.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=475186http://www.diskusjon.no/index.php?ap...tach_id=475183
Which options have you got? I'm interested in these:Quote:
Originally Posted by Christopher
Intel X25-E (old skool :D)
Plextor M2P (Marvell + 32nm Toshiba Toggle)
Average WA
60GiB (LBA) * P/E Cycles (690) = 41,400
Actual writes = 2,854
WA = 14.50
MWI 81
POH 89
Avg write speed = 4.51MiB/s
EDIT: I'll do a pure 4K only WA calculation later.
minipayne,
I do have a another X25-E 32 on the way (on its way via UPS), but it would take... Years. As in at least a few - to test. The 40GB Intel drives have well exceeded their PE cycle ratings. Who is to say that an X25-E wouldn't last 2x the PE rating? And, I believe the 32GB actually has 40GB of SLC as well, meaning its overprovisioned a fair amount out of the box. So, I think testing an E would be a time commitment I'm just not willing to make.
I am trying to get a Plextor though. The first drive I tested was a SF2281 with Toshiba toggle. The Samsung is Toggle NAND, and the a 64GB Plextor would be interesting (Marvell + Toggle) as a counterpoint to the other two drives.
I can't believe that everyone is putting the X25-E as a legendary product :) Actually my X25-E 64GB is now at 99 (normalized value) MWI with around 10 TiB host writes, 0 reallocation. I guess it's pretty safe to leave it on a server and not having to worry about any swapping between physical memory and virtual memory, if lots of users always keep submitting memory-hungry jobs to make the server run out-of-memory :)Quote:
Originally Posted by Christopher
The Plextor M2P may only come in 128GB and 256GB (but I'm not sure on this). It would be expensive to test on it if there's no 64GB model...
Christopher:
It seems you've got one more thing to play with the Samsung 830 :) There seems to be a new firmware released for it. Someone just mentioned that he updated his firmware version from CXM01B1Q to CXM02B1Q. Would this resolve the 177 updating issue and the performance drop?
http://img407.imageshack.us/img407/2392/capture18j.jpg
There is no 64GB model. Ditto for the Corsair Performance Pro (which is nearly identical to the Plextor M2P).Quote:
Originally Posted by minpayne
My 64GB X25-E is also still at 99 (see below). I was messing around with it the other day and I noticed that my locking SATA cable does not lock on the X25-E. But I couldn't see whether there was a broken plastic tab on its connector, or if it was just never designed to hold a locking SATA connector. Except for that, the X25-E is great. I've been using it for my boot drive for years now (check the power-on hours!).
Code:ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
3 Spin_Up_Time 0x0000 100 000 000 Old_age Offline - 0
4 Start_Stop_Count 0x0000 100 000 000 Old_age Offline - 0
5 Reallocated_Sector_Ct 0x0002 100 100 000 Old_age Always - 0
9 Power_On_Hours 0x0002 100 100 000 Old_age Always - 23874
12 Power_Cycle_Count 0x0002 100 100 000 Old_age Always - 188
192 Unsafe_Shutdown_Count 0x0002 100 100 000 Old_age Always - 61
232 Available_Reservd_Space 0x0003 100 100 010 Pre-fail Always - 0
233 Media_Wearout_Indicator 0x0002 099 099 000 Old_age Always - 0
225 Host_Writes_32MiB 0x0000 200 200 000 Old_age Offline - 819652
226 Intel_Internal 0x0002 255 000 000 Old_age Always - 4294967295
227 Intel_Internal 0x0002 000 000 000 Old_age Always - 281474976710655
228 Intel_Internal 0x0002 000 000 000 Old_age Always - 4294967295
Hey, good find! Here is the link:Quote:
Originally Posted by minpayne
http://www.samsung.com/us/support/do.../MZ-7PC064D/AM
Interesting. The timed workload MWI function are related to 226 & 227. It looks like the X25-E has these attributes, although they are not labelled as such. If they are timed workload attributes it would be easy to calculate how long it would take to deplete the P/E cycles.
IF Intel bring out a SF based drive presumably it will also have the timed workload function.
Well, if the new firmware update doesn't cure the speed degradation of the Samsung 830, then I guess I tend to speculate that Samsung might have employed the so-called "throttling" strategy as rumored to be used by SandForce
http://img708.imageshack.us/img708/5526/25495747.jpg
http://img266.imageshack.us/img266/4139/40365904.jpg
http://img109.imageshack.us/img109/3528/85601285.jpg
Samsung f/w update - it seems that atribute 177 can now update without a power cycle. :)
Sounds great! Now could you please log it safely, and we might be able to find if its raw value is the average P/E count or the max P/E count or something else!Quote:
Originally Posted by Ao1
This does not change what I have previously been able to report, although I can now report each incremental change in the dec value of 177.
This is the 4K random workload. I’ll switch to the client workload later when I have some time.
http://img94.imageshack.us/img94/826...wareupdate.png
Given that Micron claims to be able to secure erase an entire C400 (M4) 512 GiB within several seconds (officially within 60 seconds), I think it might actually be true that the nand writing speed can be a lot greater than the host writing speed, hence making the huge WA possible (e.g. 23x WA with 1QD 4k full span). Note that Samsung 830 has a "triple-core" controller.
^
Correct, from a random Intel NAND spec sheet:
- Random read: 50 μs
- Sequential read: 20 ns
- Write performance
- Page program: 900 μs (TYP)
- Block erase: 2 ms (TYP)
So, at NAND level a block erase = 2ms
A block (in this example using Intel NAND) = 1MB
60 GiB = 61,440 x 2ms = 122,880 ms or 123 seconds
Host writes to fill a 60GiB drive @ 160MB/s would take 384 seconds
Let’s look at what the SMART data reports
In 10 minutes host writes = 2.54 GiB
If you multiple 2.5 GiB by the WA factor the writes at NAND level = 60.04 GiB
It appears entirely plausible that the combination of host writes and block erase times could be achieved within the time frame and I remain convinced that 177 is the MWI and the decimal value = 1 complete P/E cycle.
First, there is no M2P, but there is a 64GB M2S (the earlier model, similar to the Corsair Performance 3s). It's slower, but basically the same thing.
Second, the X25-E is awesome, and I don't think you'll find too many people who disagree with that assessment (but it is not testing material -- unless you can wait 80 months for the results.)
Third, I have downloaded the new Samsung FW. It wasn't up when I checked yesterday, but I have the .ISO file so I will update the drive after todays' update, barring any objections from the peanut gallery. Wish me luck.
Lastly, I too was convinced that 177 was MWI as well, but trying to convince the SSDLife people of that didn't get anywhere. So my edition just has host writes and not MWI.
Samsung 830 64GB Update, Day 35
FW:CXM02B1Q
Upgraded after update from FW:CXM01B1Q
GiB written:
222560.85
Avg MB/s
69.34
PE Cycles
14031, up from 13669 yesterday
Reallocated Sectors
40960
20 Blocks, up from 18
869 Hours
https://www.box.com/shared/static/a8...l77umcd5sx.png
https://www.box.com/shared/static/ud...59cq8c1x0b.png
We will see what other effects the new FW has besides 177. I may SE the drive again to see if performance will go back to normal.
EDIT
Avg Speed is up quite a bit, even in the short time I have had CMX02B1Q up and running. It's increased 7MBs over the past hour.
UPDATE
I secure erased the drive, and left it idle for a few minutes. The good news is, speed seems to be back almost to where it should be. The bad news -- 177 doesn't seem to update. I still need to power cycle the drive to get 177's value.
Kingston SSDNow 40GB (X25-V)
621.78TB Host writes
Reallocated sectors : 05 21
Available Reserved Space : E8 99
POH 5617
MD5 OK
33.81MiB/s on avg (~25 hours)
--
Corsair Force 3 120GB
01 77/50 (Raw read error rate)
05 2 (Retired Block count)
B1 67 (Wear range delta)
E6 100 (Life curve status)
E7 10 (SSD Life left)
E9 678372 (Raw writes) ->662TiB
F1 902843 (Host writes) ->882TiB
MD5 OK
106.80MiB/s on avg (~25 hours)
power on hours : 2590
--
Looks like the Samsung FW update was a success, will do mine asap.
Looks like mine is now worn in :D (Will confirm WA for the normal endurance load in a bit).
http://img546.imageshack.us/img546/6867/asux.png
Wow, 141.84 MB/s, I think that is a new ASU record for a 64GB SSD.Quote:
Originally Posted by Ao1
Wonder what the 128GB Samsung (or a 256GB) would manage, probably more but not much I think.
Whoa, over a 3 hour duration of the “normal” endurance load I’m getting a WA factor of 1.04. I’m going to leave the normal endurance workload running overnight to double check and make sure as that is way lower than what I was seeing on the last f/w.
“Normal” ASU WA
60GiB (LBA) * P/E Cycles (28) = 1680
Actual writes = 1,602
WA = 1.04
Ao1,
Mine doesn't seem to be updating 177 correctly after the FW update either, so you may want to double check.
My drive is faster at the moment, but not back up to the speeds you're getting. Mine was like that before I hit the unassailable performance barrier. Now I'm happy with 130MBs. But even in the beginning, I couldn't get 160MB/s in the endurance test for very long. Basically, my average dropped to 110MBs after a while.