Printable View
Patriot Torqx-2 64GB - Day 27
Drive hours: 647
GiB written: 39,178.00 GiB (38.2599 TiB)
Avg MB/s: 19.21 MB/s
Bad blocks: 2/0/83
Wear cycle counter: 0/2506/3778
Intel 520 60GB - Day 18
Drive hours: 450
Avg MB/s: 93.14 MB/s
Host GB written (F1): 133,914.47 GiB (130.78 TiB, 4285263 raw)
NAND writes (F9): 94,832 GiB (92.61 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Media Wearout Indicator (E9): 71
Kingston SSDNow 40GB (X25-V)
790.03TB Host writes
Reallocated sectors : 05 30
Available Reserved Space : E8 99
POH 7093
MD5 OK
33.99MiB/s on avg (~71 hours)
I had to reboot the computer again as I was about go on a business trip and had to check that TeamViewer was working :)
I'll post updates but it probably won't be on a daily basis.
Vertex Turbo 64 Day 16
114364.97GiB
83.27MB/s over 390.61 hours
2048 Average Erase Count
60 MWI
389 POH
0/0/0 Program/Erase/Read Failures
Vertex Turbo 64 Day 16
114364.97GiB
83.27MB/s
2048 Average Erase Count
60 MWI
389 hours
0/0/0 Program/Erase/Read Failures
Patriot Torqx-2 64GB - Day 28
Drive hours: 671
GiB written: 41,408.00 GiB (40.4375 TiB)
Avg MB/s: 19.21 MB/s
Bad blocks: 2/0/83
Wear cycle counter: 0/2588/3901
Intel 520 60GB - Day 19
Drive hours: 473
Avg MB/s: 93.16 MB/s
Host GB written (F1): 140,205.09 GiB (136.92 TiB, 4486563 raw)
NAND writes (F9): 99,289 GiB (96.96 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Media Wearout Indicator (E9): 70
Had windows update come along and mess up my ASU counters again.
I've switched to calculating the Torqx 2 GB written by multiplying the second int of attribute "wear cycle counter" by 16, which seems realitively accurate. (but not perfectly)
Kingston SSDNow 40GB (X25-V)
794.66TB Host writes
Reallocated sectors : 05 30
Available Reserved Space : E8 99
POH 7133
MD5 OK
33.66MiB/s on avg (~111 hours)
@canthearu
You can get it to recalculate the summary.
How can I get it to anvil?
Kingston SSDNow 40GB (X25-V)
800.03TB Host writes
Reallocated sectors : 05 30
Available Reserved Space : E8 99
POH 7189
MD5 OK
31.77MiB/s on avg (~167 hours)
@canthearu
Double-click inside the (TiB Written box) and restart the app. (You should get a message box that telling you to restart)
Vertex Turbo 64 Day 18
139060.48GiB
83.56MB/s
2492 Average Erase Count
51 MWI
473 hours
0/0/0 Program/Erase/Read Failures
This thread just hit 1,000,000 views! To commemorate the event, it's time for a new drive...
Kingston SSDNow 40GB (X25-V)
804.42TB Host writes
Reallocated sectors : 05 30
Available Reserved Space : E8 99
POH 7227
MD5 OK
32.02MiB/s on avg (~205 hours)
--
> 1.000.000 views is rather nice :)
I'll decide on what SSD to test when I get back home. (in about 2 weeks)
(Corsair Force 3 120GB, Intel 320 80GB, Crucial C300 are amongst the candidates)
Patriot Torqx-2 64GB - Day 33
Drive hours: 790
GiB written: 49,808.00 GiB (48.64 TiB)
Avg MB/s: 19.72 MB/s
Bad blocks: 2/0/83
Wear cycle counter: 0/3113/4710
Intel 520 60GB - Day 24
Drive hours: 591
Avg MB/s: 91.59 MB/s
Host GB written (F1): 178401.88 GiB (174.22 TiB, 5708860 raw)
NAND writes (F9): 126,346 GiB (123.38 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Media Wearout Indicator (E9): 61
Attachment 124714
@canthearu
Did you get the counter working?
--
I'll check out where B.A.T is, haven't seen him posting lately.
No, I mean, I have a new drive.
I'm waiting until the 24hr mark before I post the first update.
It was either this drive, or the Plextor M3P 128 I just got.
I got that Christopher :)
I'll be adding one as well, when I get back home.
I've got an M2P but I don't consider using it for Endurance testing, it's currently a boot drive and will stay so for a while.
(it feels just like any other drive but I consider the SMART attributes to be inadequate for testing at this point)
No, the M3P's are useless for smart data. But it's pretty damn fast all the same...
If the Marvell partners get some new FW in the coming months which rectifies some of those issues, I'll run it.
But if I wasn't familiar with the performance of the M3P or the Intel 510, and I was asked which one I felt was faster, I'd say the Intel 510. Somehow, the 510 is what you would get if Intel decided to make a drive just for my day-to-day tasks.
-----------
FYI --
I bought one more old-new-stock MTRON. A 7500 PRO, and it's QD1 4K reads are fantastic. It's sequential writes are much faster as well. 4KRW is not improved, but it's just more MTRON-y.
But I've lost all taste for those things, at least as far as endurance testing goes. I will take it apart at some point to see what's inside.
I know it's doing something different as the FW is the same.
Anvil: Nope, double-clicking on the TiB written box does nothing. Clicking on the GiB written box brings up a message, but after restarting, the GiB written isn't fixed.
New Drive Time!
Samsung 830 256GB Day 0
I can't believe I'm about to sentence another innocent drive to a life sentence of hard labor. What can I say? I'm out of control.
Here is a shot about 16 hours in to the process:
https://www.box.com/shared/static/ab...df4b9d7893.png
I've been studying the initial problem I had with the first drive. I think I have it figured out.
Basically, if it does not happen to this drive, I have it solved. If it does happen -- back to the drawing board.
I won't go nutty with the benches, so here's one:
Attachment 124721
From the perspective of speed vs. capacity, it's like having a 64GB drive doing 73MB/s (like the M4). It's just barely possible.
It's clocking about 293MB/s average -- and a TB per hour. It will take a couple days to get to the point where I can determine whether 177 is updating properly, but so far it look like it.
I was hoping for a little more speed though. It's averaging around 330MB/s thoughout the loop, not as close as the 64GB was to it's max write, but I don't know that it's a fair comparison.
Just wanted to drop a line in here to take the time to thank everybody for making this possible.
Anvil for the software code and the volunteers for the SSDs.
Sad to be stuck in the peanut gallery but ATM I cannot change that.
Has anybody considered using Linux for these tests with a more automated reporting setup etc. ?
You mean, like a robot that will just post updates on XS for me? I'm looking in to it. ;)Quote:
Originally Posted by bulanula
Christopher:
Nice speed you are getting from the samsung.
My 240gig Sandisk extreme (got it yesterday) is only 160meg per sec in ASU endurance (should spend a little bit of time figuring out why speed is so low, could be due to sata 2 and microsoft drivers)
And I do think you are crazy for throwing a 256gig drive on the fire :) ... but I guess it was bound to happen sooner or later!
I'm probably going to get thrown under the jail for doing this to a 256GB drive. It's not quite 19 hours in and I already have 21 000GiB written. Just... awesome.Quote:
Originally Posted by canthearu
I almost bought a Extreme 120 (They were seriously cheap here for a day... ) but I decided on the Plextor M3P 128. I just figured the incompressible writes were not going to be stellar on the SDEx, no matter what.
My Mushkin Chronos Deluxe 120GB has a max seq. random data write of 240MB/s... but it can only manage 180MB/s with 47% data in ASU. SF writes are funny under the best of circumstances... a sawtooth-like wave keeping avg. speed low. It's the nature of the beast, but not a big deal under normal use. In the endurance test, sometimes you just need a bigger hammer.
Yeah, they are, but the Extreme 240gig cost $329 and I just couldn't pass that up. Besides, the reads are always very quick (both compressed and incompressed) and in real use, I have no data source that can approach the maximum write speed of this drive. The write performance is only the bottleneck in benchmarks and ASU :)Quote:
Originally Posted by Christopher
@Christopher,
Yes, you are definitely crazy...but it a good way...thanks for the 256 tester!
You are most welcome, Bluestang.