HD Tune Pro
Version and / or Patch Used: 3.00
Developer Homepage: http://www.efdsoftware.com/
Product Homepage: http://www.hdtune.com/>
HD Tune is a Hard Disk utility which has the following functions:
- Benchmark: measures the performance
- Info: shows detailed information
- Health: checks the health status by using SMART
- Error Scan: scans the surface for errors
- Temperature display
HD Tune Pro gives us accurate read, write and access time results and for the last couple of years has been gaining popularity amongst reviewers. It is now considered a must have application for storage device testing.
Samsung single drive on NVIDIA 680i
Samsung single drive on Areca
2-Drive RAID 0
3-Drive RAID 0
3-Drive RAID 5
4-Drive RAID 0
There is a lot of information here for us to take in.
Let's start with the Areca controller and how it affects the numbers. As you can see, the Burst Rate on all of the tests with the controller has gone through the roof. The controller features a user upgradable cache module that allows a portion of data to be stored in fast memory, and this will affect the Burst, Maximum and Average scoring for the better.
When looking at the scores from a single drive on the Areca controller and a single drive on the NVIDIA 680i SLI chipset, we see that the controller is far more efficient at transferring data, even in the Minimum category.
The next thing to look at are the RAID 0 numbers. The Samsung SATA-II drives scale very well when used in RAID 0 and all of the numbers nearly double just by adding another drive. We tested up to four drives and had very good results.
RAID 5 was thrown in, just because we could. It is unlikely anyone would run RAID 5 outside of an enterprise environment, but we had the controller and the drives and thought "What the heck; let's do it". The performance of a RAID 5 array with three drives is similar to that of RAID 0 with two drives. This was expected and in the read category we didn't encounter any ill effects.
RAID 5 is notorious for turning write speeds to mush, so let's move on to see what happens when we run the same tests but with write data instead of read data.