Yeah, I'll get on that, but I'm using a polling period of 1 hour.Quote:
Originally Posted by Ao1
Printable View
Yeah, I'll get on that, but I'm using a polling period of 1 hour.Quote:
Originally Posted by Ao1
As long as there is a defined polling period and an amount of data written between that time it will work. One hour = less data entry points which will make the graph easier to work with, but then again if the speed drops are less than one hour you will lose granularity, although you would still see the average drop over the hour.
I'll make a note about the Velox.Quote:
Originally Posted by canthearu
The 330 could be a candidate, as is the Vertex 4 :)
Here is a quick and dirty chart I made for the last 85 hours.
https://www.box.com/shared/static/07...b5c1d21a20.png
For best results, just open the picture in a new tab.
I should also integrate temperature data too.
I don't know how useful the chart I made is, but I just wanted to make it look good.
Incidentally, that dip around Hour 25 is probably when I removed the drive for ~20 mins. I had it in and out in between polling, but I forgot to start it back for another 15 minutes or so. I'll try and make a chart integrating that data and temperature. I think it would be more interesting.
Style > Substance
It will be a great shame once the samsung kicks the bucket ... it is such an awesome performing drive.
Pitty it is so damn expensive around here ($440AU for a 256g drive)
I upgraded another 830 I have from 01FW to 03FW and got a significant performance bump, mainly with writes.Quote:
Originally Posted by canthearu
I don't know what the exchange rate is, but it's about 25% cheaper here than it was at launch last fall. The pricing is also very volatile at the moment - The 128GB has been $139 to $200 US in the past few days, and the 512GB has been as low as $640 and as much as $800 US.
------------------------------------------------------
OCZ Octane 128 Day 11
161313.13 GiB
159.54 MB/s Average
Samsung 830 256 Day 18
280963.33 GiB
279.24 MB/s Average
385 Hours
1679 Wear Leveling Count
MWI 54
0/0 Erase/Program Fail
OCZ Vertex Turbo 64 Day 37
263022.50 GiB
84.32 MB/s Avg
887 hours
4680 Avg PE count
7 MWI
0/0/0 Read/Program/Erase Fail
------------------------------------------------------
I expect it's just that you entered 280963 GiB in stead of 380963 ?Quote:
Originally Posted by Christopher
I'm using 380963 for the chart, let me know if there is something up.
@ Anvil -- that was just a typo.
A new Chart
https://www.box.com/shared/static/40...2aacff50d1.png
Temp, Avg MB/s, Hourly GiB written, Wear Leveling Count, and MWI are all included. I'm using a logarithmic scale. Again, open it in a new tab for your viewing pleasure.
Speed and temperature are pretty much in lock-step.
i cant get it to open in another tab.
right click > view image :)Quote:
Originally Posted by Computurd
If anyone cares, I'd be happy to present the info in some other way.
OCZ Octane 128 Day 12
175520.13 GiB
159.15 MB/s Average
Samsung 830 256 Day 19
407308.33 GiB
282.14 MB/s Average
411 Hours
1793 Wear Leveling Count
MWI 50
0/0 Erase/Program Fail
OCZ Vertex Turbo 64 Day 38
269319.50 GiB
84.33 MB/s Avg
912 hours
4817 Avg PE count
4 MWI
0/0/0 Read/Program/Erase Fail
------------------------------------------------------
The 830 is now at MWI 50 and over 407,000GiB!
The Vertex Turbo is almost to MWI 1, but really when MWI = 1 it should really be MWI = 50.
The Cognac FW 1.6 or later puts all MLC PE counts at 5000, even when they should really be 10,000.
The Vertex Turbo has made it to 4900 average PE count, or MWI = 2. Min and max are 4068 and 5262 respectively.
No reallocations just yet, but surely some are bound to be around the corner.
The Super Sexy Samsung is at 426,502 GiB and 427 hours.
EDIT
the VT should hit MWI 0 in about 18 hours from now, but I don't know if it should really be MWI - 0 or MWI - 50.
Todays update:
Intel X25-M G1 80GB
482.80 TiB
22159 hours
Reallocated sectors : 25 to 42
MWI=71 to 68
MD5 =OK
43.77 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=485340
m4
656.1356 TiB
2824 hours
Avg speed 72.92 MiB/s.
AD gone from 245 to 233.
P/E 11386.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=485339
SSDLife Pro stopped working again so you just got CDI this time. The most interesting thing going on is that the Intel got reduced Reserve space as the reallocted sector count is increasing.
Patriot Torqx-2 64GB - Day 51.5
Drive hours: 1,234 (722 Hours, 512 missing)
GiB written: 80,752 GiB (78.86 TiB)
Avg MB/s: 20.10 MB/s
MD5: OK
Bad blocks: 2/0/83
Wear cycle counter: 0/5047/7730
Attachment 125132
Intel 520 60GB - Day 42.5
Drive hours: 1,033
Avg MB/s: 91.77 MB/s
MD5: OK
Host GB written (F1): 321,822.22 GiB (314.28 TiB, 10298311 raw)
NAND writes (F9): 227,858 GiB (222.52 TiB)
Reallocated sectors (05): 0
Failure count (AB, AC): 0 program, 0 erase
Media Wearout Indicator (E9): 27
Attachment 125133
Just some general comments:
The torqx 2 seems to be hanging in there. It still can't count hours, but it hasn't suffered cataclysmic problems, nor has speed dropped any. Just wish it was a bit faster because at this rate, I'll still be posting updates on it in a year's time. MD5 checks indicate that it isn't even losing data :)
The Intel continues to be boring as hell in its military precision and slow match to its own demise .... how far it goes is anyone's guess ... the NAND isn't showing any signs of disfunction. The intel 520 will probably go like many of the other drives ... by forgetting its contents one day during after a retention test.
My SSDlife stopped working too. When the VT hit MWI 0, it stopped updating. I restarted it, and now I get an improper argument error. Deleting the data file would probably solve the issue for me. I just need the program because its easier to take screenshots remotely on a touchscreen device with the screen capture button.
I got the same problem. The program is just blank but I'm able to take screenshots with teamviewer so I'll use CDI until I'm home next week.
I'll delete the info file for SSDlife and report back.
The VT is still without a reallocation after 5100 PE cycles (almost). however, bit errors seem to have increased.
Attachment 125134
see attributes CA and CB.
Same as I got on the first m4 the last 100 TiB of writing but it had over 12000 P/E.
It'll be exciting to see if it increases steadily or accelerate as you burn P/E.
I really like the Turbo's performance so far. It's looking like a completely different drive than the first one I put up, likely due to the first drive having some questionable quality flash.
Todays update:
Intel X25-M G1 80GB
485.60 TiB
22178hours
Reallocated sectors : 42 to 50
Available Reserved space: 97 to 96
MWI=68 to 67
MD5 =OK
43.70 MiB/s on avg
http://www.diskusjon.no/index.php?ap...tach_id=485450
m4
660.8916 TiB
2844 hours
Avg speed 74.50 MiB/s.
AD gone from 233 to 230.
P/E 11467.
MD5 OK.
Reallocated sectors : 00
http://www.diskusjon.no/index.php?ap...tach_id=485451
I restartet ASU on the m4 on accident but everything runs fine.