Vertex 4 F/W 1.3 vs 1.4 across ich10r, pch, Areca 1261 and 1880 and ...

[Computurd]

LSI has seemed to be on the ball with the fixes, with the latest FW it may not be an issue anymore, which is a very positive thing!

[Anvil]

I've ran a few tests using ATTO (for sequentials only) on the LSI 9265, w/o caching. (Direct IO, Write Through, No read ahead)

Keep in mind that the V3 is working with compressible data, they are in a "heavily used" state though, several TBs written to each drive w/o any cleaning (no TRIM as they are in raid) for 3-4 months, maybe more.
The m4's are set up in a raid 00 (a span of 2x raid-0) so there are 4x 128GB drives, also in a used state.

read_atto.png

write_atto.png

The V4's could do with some tuning on reads. (which can be seen in other tests as well, coming later...)

[SteveRo]

Yes, agree writes are looking nice, reads - so so ....

[SteveRo]

For fun cache run with old areca 1261

2xvertex4, f/w 1.4.1.3, 1261/2gb, 4k stripe, disk write cache mode disabled, array as boot drive, 2600k @ 4.8ghz on m4e -

[Anvil]

A quick test on FW 1.5 shows that things are looking much better on the Areca 1880IX-16 4G

There was a strange reading in ATTO (at 1KB) but compared to previous tests this is something that's worth playing with.

1880IX-V4-FW15.PNG

Areca V4-256-2R0 SCSI Disk Device_499GB_1GB-20120711-0014_FW_15.png

(the results are cached, the point is that it's working, on earlier fw's it wouldn't finish any benchmark)

I'll play a bit more too see if the ATTO anomaly at 1KB can be reproduced.

edit:
64KB strip size, Volume cache mode -> Write Back

[johnw]

For ATTO, try "Neither" instead of "Overlapped I/O"

Also, try increasing the "Total Length" to 2GB (or whatever is the max allowed)

[Anvil]

I'll do some more testing later this week/weekend.

My goal was just to see if it was working, at all

[Tiltevros]

try to set 1mb stripe size on LSI controller and see what is happening on read write sequential and 4k@64 on sandforce controller

(4xR0 1mb stripe size no cache on, direct io, no read ahead 3k kingstons)

[SteveRo]

WOW! 1.5 f/w is looking good - I will try!

edit - Hey there Mr. Tilt - nice AS SSD run there!

[SteveRo]

Looks like vertex4 compatibility with areca 1880 might be fixed with F/W 1.5.
Probably needs some time to check out completely but looking ok for the most part so far.
I did have a glitch running Anvil Storage Utility, needed to rerun the read test and then all looks as expected'
These are cache runs - 2xVertex4 128gb F/W 1.5 R0 Areca 1880 4GB on crosshair V formula with 3xcpu Phenom II X2 555 BE @ 4ghz -





For comparison here is cache run - 2xVertex4 128gb F/W 1.5 R0 Areca 1261 2GB on X58 with W3520 @ 4ghz -




Interesting that the Anvil benchmark keeps the name "ARC-1261" when switched from 1261 to 1880 - the array name is maintained as I did not recreate the array just moved the drives from 1261 to 1880

[Nizzen]

http://guru3d.com/article/ocz-vertex...-15-firmware/1

[Rubycon]

1.5 does NOT fix issue with 1880ix controllers!
The test system would get a timeout error on a reboot. A cold shutdown of the system is the only way to get it to boot properly.
I would not recommend this drive with these controllers. Intel 520, Samsung 830, and Crucial M4 (with current FW) all work flawlessly and fast.

[Anvil]

I didn't notice any such issues.

Will retry tonight.