Alright, new "Results Summary" based on Napalms new tests. A lot of it looks the same, but sentences/numbers have been changed.
Results we have seen thus far:
Napalm:
Single Drive on Areca
-----------------------
Avg Read: 78.2 [write cache on] / 78.1 [write cache off]
CPU: 0%
Random Access: 8.1ms
Burst: 750.9MB/s [write cache on] / 756.7MB/s [write cache off]
Single Drive on Onboard
----------------------
Avg Read: 77.3MB/s
CPU: 2%
Random Access: 8.1ms
Burst: 137.1MB/s
RAID-1 on Areca
-----------------
Avg Read: 77.8MB/s
CPU: 0%
Random Access: 8.7ms
Burst: 745.2MB/s
RAID-1 on HP Card
-----------------
Write back cache on:
Avg Read: 88.5MB/s [write cache on] / 78.2 [write cache off]
CPU: 0%
Random Access: 7.6ms [write cache on] / 7.4 [write cache off]
Burst: 1307.5MB/s [write cache on] / 135.7 [write cache off]
Myself
Single drive on TX2300:
Avg Read: 65MB/s
CPU: 2%
Random Access: 7.7ms
Burst: 114.0MB/s
RAID-1 on TX2300:
Avg Read: 65MB/s
CPU: 2%
Random Access: 6.8ms
Burst:126.5MB.s
My analysis:
Avg Read Time:
My average read time remained a steady 65-65.1MB/s in all my tests. Napalms fluxuated somewhat with write caching on/off, but that's to be expected. His drives, on hardware controllers, pulled an average of 78.16MB/s, and his onboard test gives 77.3MB/s. Realistically, those two numbers are so comparable the difference could just be the difference between one run and another.
The bottom line here is that in RAID-1, his controller did not confer any benefits to him over my software-driven add-on card.
CPU Utilization:
The battle here seems to be between mine at 2% and his being reported at 0%. I think we can agree that just running the program involved some kind of resources, so if you'll allow, I'd like to argue it's my 2% (HD Tach) versus his 0.4% (his lowest HD Tune). If not, fine - his program runs without resources. In either event, I'll add that his processor is at least a Q6700 - overclocked to 3.6GHz in one of his posts in another thread - where the one I'm using for this test bed is a dual-core Opty 170 at stock speeds that my wife has been using for the past year or so (and loaded it with garbage, but that's another story).
Given the performance difference between a 3.6GHz Core 2 Quad and a 2.0GHz Opteron 170... I think we can agree that the utilization is next to nothing for both solutions.
Seek time:
In his testing, Napalm went UP in access times with an Areca card and down with his HP. His single-drive access time is 8.1ms. With the Areca, he was given 8.7ms response on his RAID-1 array, and with the HP pulled an average of 7.5ms. In the first case, it is an increase of 0.6ms and the second a decrease of 0.6ms. In my results, I went from 7.7ms to 6.8ms, a decrease of 0.9ms.
It is important to note, however, that although my decrease was better in absolute terms, it was also better in relative terms. His decrease on the HP represented a decrease of 7.41% average seek times, while mine was an 11.69% decrease.
Why the differences? RAID-1 with any optimizations at all should reduce speed. His HP clearly introduced some form of load balancing between the two to reduce speeds, but seems to stop there. Areca cards, however, have never been notorious for their use in RAID-1... exactly why, I'm not sure. Clearly some sort of code fix is needed. For myself though, my software solution provides me use of the elevator seek algorithm. While *only* the second-best seeking algorithm we've yet found, it's still apparently pretty good.
The only conclusion to be drawn here is this: My software RAID implements algorithms or optimizations that are not seen on his hardware RAID card.
Burst speeds:
In terms of Napalms results, well they're obviously a function of it having actual RAM cache. 'nuff said there. Mine weren't great, but I was bottlenecked by the PCI bus as well, so I can't really make a fair comparison.
Final thoughts:
Well, I hope I've demonstrated the following:
1. Sustained Read Speed: Napalms sustained reads were faster, but so were his drives. His hardware card did not improve speeds noticeably (0.86MB/s). There is no speed advantage to be taken by hardware cards here.
2. CPU Utilization: With a comparable CPU, this should be negligible either way
3. Seek times: My card was the clear winner, both absolutely and relatively (0.9ms / 11.69% drop versus either 0.6ms / 7.41% [HP] OR an Increase [Areca]).
4. Burst speeds: RAM cache versus a PCI bus... no contest there
So I invite you Naplam and itznfb - what do you say? For RAID-1/0, can we be agreed that - for a limited number of drives - software-based solutions* are the equal and can in fact be the superior to hardware-based solutions but at a fraction of the price?
*Edit: (at least those which use add-on cards, not necessarily on-board junk)
With that said, hardware cards do certainly provide:
- The ability to migrate to RAID-5/6
- Additional cache, which can be a benefit in *some* desktop usage patterns
- The ability to scale further (in general, due to software-based cards being generally limited to the PCI and PCI-E x1 busses)



Reply With Quote




Bookmarks