 |
|
Promise FastTrak100 vs. AMI MegaRAID IDE100
Introduction
Our last RAID review took a look at two hardware ATA RAID controllers: the SuperTrak100 and Escalade 6400. As discussed there, the presence of an on-board RISC processor on both of these cards earned them the "true hardware RAID" classification - RAID cards without a dedicated processor are oftentimes called "firmware RAID" as all RAID calculations are done by the system's main processor.
This time around we're going to compare two lower-cost "firmware" solutions: the Promise FastTrak100 and the AMI MegaRAID IDE100 (formally known as the HyperDisk 100). Both of these cards retail for under $100 - far less expensive than hardware cards like the SuperTrak and Escalade.
Needless to say, this price differential raises the issue of performance. If firmware RAID cards like the FastTrak and MegaRAID perform as well as hardware RAID adapters such as the SuperTrak and Escalade, there's little incentive to pay much more for one of the latter cards. If performance differences are significant, however, then one would have to consider each card's price/performance ratio before deciding which one to buy.
Before assessing the performance of each card, let's take a closer look at the adapters themselves.
The FastTrak100...
The FastTrak series of RAID adapters is undoubtedly the most well known of them all - it's primarily this series that enabled Promise to attain a 90% share of the ATA RAID market over the last few years. The FastTrak100, up until a couple weeks ago, was the newest version of this popular line (see our news post about Promise's FastTrak100 TX & LP announcment), allowing ATA-100 support via Promise's ATA-100 ASIC.
FastTrak 100 Specifications...
- RAID levels 0, 1, 01, and JBOD; (Just a Bunch Of Disks... serially linked into one capacity)
- Up to 4 ATA-100 drives supported (2 ATA channels);
- "Hot spare" capability;
- Stripe size selectable from 1K to 1MB;
- S.M.A.R.T. support for reporting pending disk drive failures;
- Easy upgrade of current disk drive to a RAID 1 array by automatically duplicating existing data to the array;
- Support for BIOS Boot Specification (BBS);
- DOS / Win3.1 / 9x / ME / NT / 2000 support;
- 2-year warranty
Included with the Promise are the following items:
- Two dual-connector, 80-conductor ATA cables;
- ~90 page user manual (can be downloaded here).
- Driver and utility disks
The Software...
The FaskTrak 100's BIOS - a.k.a. FastBuild - facilitates standard functions such as array creation, deletion, and status viewing. RAID 0 arrays may be configured with one to four drives (a 1-drive RAID 0 array represents a standard single-drive configuration), RAID 1 arrays can be configured with two drives (with one or two hot spares also configurable), while RAID 01 arrays must have four drives. Stripe size for RAID 0 and RAID 01 arrays can be between 1K and 1MB (logarithmic intervals), and any array may be made bootable if the user so desires. Also notable is that a RAID 1 array can be configured from an existing drive without any data loss. This is a convenient feature for those who want to add redundancy to an existing drive.
The FastTrak also comes with FastCheck, a utility that monitors and configures arrays from within Windows. With FastCheck, one may view array details, perform synchronization of a RAID 1 array, rebuild a degraded RAID 1/01 array, and configure a plethora of options including S.M.A.R.T enable/disable, write cache enable/disable (refers to the write cache of the drives themselves), rebuild rate (the rate at which a degraded array is rebuilt when a spare drive is made available), PCI bus utilization, and what action to take if an error is encountered during a rebuild or synchronization procedure.
The MegaRAID IDE100...
Though not as well known as the FastTrak series, AMI's MegaRAID series of cards (known as HyperDisk up until recently) targets the exact same market: cost-sensitive ATA RAID. Announced in July of 2000, the MegaRAID IDE100 positions itself as a direct competitor to the FastTrak100.
MegaRAID IDE100 Specifications...
- RAID levels 0, 1, 10, and JBOD;
- Supports two channels and up to four drives;
- "Hot spare" capability;
- Stripe size selectable from 32K to 4MB;
- Support for BBS (BIOS boot specification);
- S.M.A.R.T. support;
- Special handling of error log, spare drive, and rebuilding;
- DOS / Win 9x / NT / 2000 / Red Hat Linux 6.1 & 6.2 support;
- 1-year warranty
Included with the card are the following items:
- Two dual-connector, 80-conductor ATA cables;
- CD with utilities and user manual;
- Driver disk
Note that the MegaRAID IDE100's user guide is on a CD rather than in print. We find it irritating to have to put the CD in every time you wish to consult the user guide.
The Software...
As with the FastTrak, MegaRAID IDE100's BIOS facilitates creation, views, and deletion of arrays. Available stripe sizes range from 32K to 4MB. The following options may be toggled per array: write cache enable/disable (as with the FastTrak, this refers to the write cache of the drives themselves), boot sector virus protection enable/disable, DMA enable/disable, and array bootable yes/no.
The MegaRAID's IDE100 software utility is, interestingly enough, still called "HyperDisk Console." The utility displays information about the controller(s), drives, and arrays. Several options may be toggled including 'Start rebuilding if error threshold reached,' 'Check arrays for rebuild at startup,' 'Make contents of the array drives identical after consistency errors found,' and 'Enable SMART on physical drives.' The utility also features "Spy Service," an array status icon on the user's taskbar. The icon turns green when all arrays are ok, yellow when there are errors, and red to "warn of a critical problem which could cause the system to fail." Finally, the utility can maintain a log of any array-related errors.
The Benchmarks...
Note: Our RAID testing methodology was disclosed in Battle Of The Titans: The Promise SuperTrak100 vs. 3ware's Escalade 6400.
For the following benchmarks, the "write cache" setting of both cards was enabled. The MegaRAID's DMA setting was enabled, and tests were done using a stripe size of 64k for both cards. The FastTrak was tested with driver version 1.30 (Build 33) and BIOS version 1.30 (Build 12), while the MegaRAID was tested with driver version 2.40 and BIOS version 2.410.
WinBench results...
Let's examine base, single drive scores for each card to establish a baseline against which RAID arrays may be compared.
|
|
| Benchmark |
Single-Drive Base Scores |
| Abit's SL6 on-board ATA | Promise Ultra66 | MegaRAID IDE100 | FastTrak 100 |
|
| Business Disk WinMark 99 (KB/sec) |
6484 |
5820 |
6304 |
6128 |
| High-End Disk WinMark 99 (KB/sec) |
16220 |
14460 |
15740 |
15400 |
| AVS/Express 3.4 (KB/sec) |
13600 |
13160 |
16260 |
15320 |
| FrontPage 98 (KB/sec) |
65860 |
50980 |
61980 |
62520 |
| MicroStation SE (KB/sec) |
21480 |
18320 |
20880 |
20520 |
| Photoshop 4.0 (KB/sec) |
8534 |
8668 |
8618 |
8598 |
| Premiere 4.2 (KB/sec) |
14760 |
12440 |
14320 |
13860 |
| Sound Forge 4.0 (KB/sec) |
18540 |
16040 |
15620 |
15200 |
| Visual C++ (KB/sec) |
17000 |
14200 |
14600 |
14460 |
|
| Disk/Read Transfer Rate | StorageReview.com |
|---|
| Beginning (KB/sec) |
29800 |
29733 |
29800 |
29667 |
| End (KB/sec) |
17500 |
17500 |
17500 |
17433 |
|
| Disk Access Time (ms) |
15.2 |
15.3 |
15.2 |
15.1 |
|
| Disk CPU Utilization (%) |
2.9 |
3.0 |
4.8 |
3.0 |
| |
The only thing that stands out about the above scores is the MegaRAID's significantly higher CPU utilization... upwards of 2% higher than that of the FastTrak. This wouldn't likely be noticeable to users, but it's interesting nonetheless.
WinBench RAID 0 scores...
|
|
| Benchmark |
2 Drives, RAID 0 |
|
3 Drives, RAID 0 |
|
4 Drives, RAID 0 |
| MegaRAID IDE100 |
FastTrak 100 |
MegaRAID
IDE100 |
FastTrak 100 |
MegaRAID IDE100 |
FastTrak 100 |
|
| Business Disk WinMark 99 (KB/sec) |
6176 |
6124 |
|
6236 |
6180 |
|
6340 |
6356 |
| High-End Disk WinMark 99 (KB/sec) |
18100 |
9424 |
19340 |
10700 |
19200 |
8652 |
| AVS/Express 3.4 (KB/sec) |
16020 |
17280 |
16840 |
16740 |
15042 |
17420 |
| FrontPage 98 (KB/sec) |
62100 |
61380 |
17960 |
62180 |
61540 |
61880 |
| MicroStation SE (KB/sec) |
19060 |
19000 |
14920 |
18480 |
17420 |
17380 |
| Photoshop 4.0 (KB/sec) |
11780 |
4502 |
14540 |
5096 |
15880 |
3886 |
| Premiere 4.2 (KB/sec) |
16880 |
5858 |
18300 |
7346 |
17620 |
5716 |
| Sound Forge 4.0 (KB/sec) |
18760 |
8350 |
19740 |
9396 |
19340 |
6866 |
| Visual C++ (KB/sec) |
17300 |
10780 |
17680 |
12100 |
17740 |
10508 |
|
| Disk/Read Transfer Rate | StorageReview.com |
|---|
| Beginning (KB/sec) |
59467 |
58700 |
|
75567 |
80600 |
|
76567 |
80667 |
| End (KB/sec) |
34933 |
34667 |
52200 |
51667 |
69767 |
68467 |
|
| Disk Access Time (ms) |
15.0 |
15.1 |
|
15.2 |
15.4 |
|
14.9 |
14.8 |
|
| Disk CPU Utilization (%) |
4.7 |
3.0 |
|
4.8 |
3.1 |
|
90.4 |
88.7 |
| |
- AMI MegaRAID IDE100, RAID 0, 2 Drive STR Graph
- Promise FastTrak 100, RAID 0, 2 Drive STR Graph
- AMI MegaRAID IDE100, RAID 0, 3 Drive STR Graph
- Promise FastTrak 100, RAID 0, 3 Drive STR Graph
- AMI MegaRAID IDE100, RAID 0, 4 Drive STR Graph
- Promise FastTrak 100, RAID 0, 4 Drive STR Graph
Several notables... First, each card's Business Disk Winmark performance in RAID 0 remains virtually unchanged from its single-drive performance. Does this imply no performance improvement in RAID 0 with both of these cards? Unlikely, so we'll avoid drawing such a conclusion until we go over additional results.
The High-End Disk Winmarks, however, are another story. The MegaRAID's scores do indeed scale somewhat in RAID 0... and we do believe they are representative of performance. The FastTrak's High-End scores, however, are far too low to be believable, and are almost certainly the result of the same WinBench Disk Winmark issue we encountered in the Escalade 6400 vs. SuperTrak 100 article. This prevents us from comparing the two cards here.
When it comes to sustained transfer rates, both cards scale quite nicely when going from a single drive to 2 and 3-drive RAID 0 arrays. Neither card, however, yields an STR improvement when going from 3 to 4 drives - the FastTrak limits transfers to around 80MB/sec, while the MegaRAID limits around 76MB/sec.
As far as CPU utilization goes, the FastTrak consistently scores 1.50-1.75% better than the MegaRAID in this area. As with the Escalade 6400 vs. SuperTrak 100 review, WinBench reports ridiculously high CPU utilization in 4-drive RAID 0 arrays. As mentioned in that review, we believe this to be a flaw in WinBench itself.
WinBench RAID 1 scores...
|
|
| Benchmark |
2 Drives, RAID 1 |
| MegaRAID IDE100 |
FastTrak 100 |
|
| Business Disk WinMark 99 (KB/sec) |
6304 |
4450 |
| High-End Disk WinMark 99 (KB/sec) |
15400 |
2920 |
| AVS/Express 3.4 (KB/sec) |
15900 |
15340 |
| FrontPage 98 (KB/sec) |
60860 |
49020 |
| MicroStation SE (KB/sec) |
21100 |
19840 |
| Photoshop 4.0 (KB/sec) |
8626 |
1056 |
| Premiere 4.2 (KB/sec) |
13380 |
1614 |
| Sound Forge 4.0 (KB/sec) |
14900 |
2370 |
| Visual C++ (KB/sec) |
14360 |
3734 |
|
| Disk/Read Transfer Rate | StorageReview.com |
|---|
| Beginning (KB/sec) |
29800 |
29567 |
| End (KB/sec) |
17500 |
17400 |
|
| Disk Access Time (ms) |
15.2 |
13.6 |
|
| Disk CPU Utilization (%) |
4.7 |
3.1 |
| |
In RAID 1, the MegaRAID exhibits little improvement over a single drive. This indicates that the adapter doesn't balance requests between the two drives in the array. Given the MegaRAID's cost-sensitive nature, this should be no surprise.
Unfortunately, the FastTrak's High-End Disk Winmark scores continue to be blatantly unrepresentative, and are therefore useless for comparison purposes. The FastTrak's Business Disk Winmark scores, however, while at first glance looking suspicious, may indeed be accurate - as we'll see later, IOMeter backs them up to an extent.
Also of interest is the Fastrak's significantly lower RAID 1 average access time. This would be expected if the FastTrak balanced loads between the 2 array drives; however, we see no other indications that any balancing is occurs - the FastTrak's Business Diskmark, STR, and (as we'll see) IOMeter scores in RAID 1 don't concur.
WinBench RAID 01/10 scores...
|
|
| Benchmark |
4 Drives, MegaRAID IDE100 in RAID 10, FastTrak 100 in RAID 01 |
| MegaRAID IDE100 |
FastTrak 100 |
|
| Business Disk WinMark 99 (KB/sec) |
6020 |
4302 |
| High-End Disk WinMark 99 (KB/sec) |
17420 |
3080 |
| AVS/Express 3.4 (KB/sec) |
15320 |
14820 |
| FrontPage 98 (KB/sec) |
60080 |
50180 |
| MicroStation SE (KB/sec) |
18340 |
17600 |
| Photoshop 4.0 (KB/sec) |
11460 |
1136 |
| Premiere 4.2 (KB/sec) |
16160 |
1696 |
| Sound Forge 4.0 (KB/sec) |
17780 |
2506 |
| Visual C++ (KB/sec) |
16680 |
3894 |
|
| Disk/Read Transfer Rate | StorageReview.com |
|---|
| Beginning (KB/sec) |
59067 |
59267 |
| End (KB/sec) |
34933 |
34800 |
|
| Disk Access Time (ms) |
15.1 |
13.3 |
|
| Disk CPU Utilization (%) |
4.7 |
3.1 |
| |
Although the MegaRAID's RAID 10 business Disk Winmark score comes in lower than that of a single drive, its High-End Diskmark score is indeed higher, likely due to doubling of STR. WinBench also reports a slightly lower access time relative to a single drive; this may be within the test's margin of error.
As far as the FastTrak goes, the Diskmark scores are obviously not representative of performance. They are simply abysmal, despite a high STR and significantly lower reported access time than that of a single drive.
IOMeter scores...
As was the case in the Escalade 6400 vs. SuperTrak 100 article, we're pleased to deploy IOMeter for a more reliable performance picture of these adapters. Due to WinBench's problems, we can't compare any of the above Diskmark scores with each other to ascertain performance differences between the two units. With IOMeter, however, we may do so.
Base scores...
|
| IOMeter Tests | IO/sec | MB/sec | Response Time | CPU Util. | IO/CPU% |
| Load = Linear |
|
Abit SL6, 1 Drive | 64.11 |
0.70 |
15.59 ms |
0.76 % |
84.36 |
|
Promise Ultra 66, 1 Drive | 65.51 |
0.69 |
15.26 ms |
0.70 % |
93.59 |
|
AMI MegaRAID IDE100, 1 Drive | 65.57 |
0.70 |
15.24 ms |
1.16 % |
56.53 |
|
Promise FastTrak 100, 1 Drive | 65.53 |
0.71 |
15.25 ms |
0.75 % |
87.37 |
| Load = Very Light |
|
Abit SL6, 1 Drive | 66.91 |
0.73 |
59.77 ms |
0.75 % |
89.21 |
|
Promise Ultra 66, 1 Drive | 67.85 |
0.73 |
58.94 ms |
0.73 % |
92.95 |
|
AMI MegaRAID IDE100, 1 Drive | 68.39 |
0.74 |
58.48 ms |
1.20 % |
56.99 |
|
Promise FastTrak 100, 1 Drive | 68.14 |
0.73 |
58.69 ms |
0.75 % |
90.85 |
| Load = Light |
|
Abit SL6, 1 Drive | 76.83 |
0.85 |
208.21 ms |
0.87 % |
88.31 |
|
Promise Ultra 66, 1 Drive | 78.11 |
0.85 |
204.80 ms |
0.89 % |
87.76 |
|
AMI MegaRAID IDE100, 1 Drive | 79.11 |
0.87 |
202.22 ms |
1.43 % |
55.32 |
|
Promise FastTrak 100, 1 Drive | 78.78 |
0.86 |
203.05 ms |
0.93 % |
84.71 |
| Load = Moderate |
|
Abit SL6, 1 Drive | 86.75 |
0.95 |
737.33 ms |
1.04 % |
83.41 |
|
Promise Ultra 66, 1 Drive | 87.72 |
0.94 |
729.34 ms |
1.02 % |
86.00 |
|
AMI MegaRAID IDE100, 1 Drive | 88.84 |
0.95 |
720.02 ms |
1.62 % |
54.84 |
|
Promise FastTrak 100, 1 Drive | 88.71 |
0.96 |
720.95 ms |
1.11 % |
79.92 |
| Load = Heavy |
|
Abit SL6, 1 Drive | 94.68 |
1.02 |
2703.59 ms |
1.48 % |
63.97 |
|
Promise Ultra 66, 1 Drive | 96.97 |
1.05 |
2634.26 ms |
1.53 % |
63.38 |
|
AMI MegaRAID IDE100, 1 Drive | 97.30 |
1.05 |
2624.96 ms |
2.05 % |
47.46 |
|
Promise FastTrak 100, 1 Drive | 97.29 |
1.05 |
2624.04 ms |
1.40 % |
69.49 |
|
|
|
| IOMeter Tests | IO/sec | MB/sec | Response Time | CPU Util. | IO/CPU% |
| Load = Linear |
|
Abit SL6, 1 Drive | 75.20 |
0.59 |
13.29 ms |
0.84 % |
89.52 |
|
Promise Ultra 66, 1 Drive | 76.05 |
0.59 |
13.14 ms |
0.81 % |
93.89 |
|
AMI MegaRAID IDE100, 1 Drive | 76.87 |
0.60 |
13.00 ms |
1.44 % |
53.38 |
|
Promise FastTrak 100, 1 Drive | 77.05 |
0.60 |
12.97 ms |
0.87 % |
88.56 |
| Load = Very Light |
|
Abit SL6, 1 Drive | 77.47 |
0.61 |
51.63 ms |
0.76 % |
101.93 |
|
Promise Ultra 66, 1 Drive | 77.96 |
0.61 |
51.30 ms |
0.81 % |
96.25 |
|
AMI MegaRAID IDE100, 1 Drive | 79.13 |
0.62 |
50.54 ms |
1.44 % |
54.95 |
|
Promise FastTrak 100, 1 Drive | 79.52 |
0.62 |
50.30 ms |
0.99 % |
80.32 |
| Load = Light |
|
Abit SL6, 1 Drive | 88.26 |
0.69 |
181.26 ms |
1.00 % |
88.26 |
|
Promise Ultra 66, 1 Drive | 88.49 |
0.70 |
178.74 ms |
1.03 % |
85.91 |
|
AMI MegaRAID IDE100, 1 Drive | 91.39 |
0.71 |
175.03 ms |
1.60 % |
57.12 |
|
Promise FastTrak 100, 1 Drive | 91.02 |
0.71 |
175.69 ms |
1.09 % |
83.50 |
| Load = Moderate |
|
Abit SL6, 1 Drive | 98.92 |
0.77 |
646.73 ms |
1.05 % |
94.21 |
|
Promise Ultra 66, 1 Drive | 99.85 |
0.78 |
640.55 ms |
1.14 % |
87.59 |
|
AMI MegaRAID IDE100, 1 Drive | 101.90 |
0.80 |
627.75 ms |
1.90 % |
53.63 |
|
Promise FastTrak 100, 1 Drive | 102.08 |
0.80 |
626.73 ms |
1.20 % |
85.07 |
| Load = Heavy |
|
Abit SL6, 1 Drive | 110.14 |
0.86 |
2320.72 ms |
1.52 % |
72.46 |
|
Promise Ultra 66, 1 Drive | 110.34 |
0.86 |
2316.28 ms |
1.66 % |
66.47 |
|
AMI MegaRAID IDE100, 1 Drive | 111.10 |
0.87 |
2300.29 ms |
2.47 % |
44.98 |
|
Promise FastTrak 100, 1 Drive | 111.46 |
0.87 |
2293.11 ms |
1.68 % |
66.35 |
|
|
|
| IOMeter Tests | IO/sec | MB/sec | Response Time | CPU Util. | IO/CPU% |
| Load = Linear |
|
Abit SL6, 1 Drive | 68.64 |
0.54 |
14.56 ms |
0.69 % |
99.48 |
|
Promise Ultra 66, 1 Drive | 76.05 |
0.59 |
13.14 ms |
0.81 % |
93.89 |
|
AMI MegaRAID IDE100, 1 Drive | 69.91 |
0.55 |
14.30 ms |
1.23 % |
56.84 |
|
Promise FastTrak 100, 1 Drive | 70.01 |
0.55 |
14.28 ms |
0.80 % |
87.51 |
| Load = Very Light |
|
Abit SL6, 1 Drive | 70.33 |
0.55 |
56.87 ms |
0.74 % |
95.04 |
|
Promise Ultra 66, 1 Drive | 77.96 |
0.61 |
51.30 ms |
0.81 % |
96.25 |
|
AMI MegaRAID IDE100, 1 Drive | 72.02 |
0.56 |
55.53 ms |
1.38 % |
52.19 |
|
Promise FastTrak 100, 1 Drive | 72.20 |
0.56 |
55.39 ms |
0.83 % |
86.99 |
| Load = Light |
|
Abit SL6, 1 Drive | 79.27 |
0.62 |
201.79 ms |
0.87 % |
91.11 |
|
Promise Ultra 66, 1 Drive | 88.49 |
0.70 |
178.74 ms |
1.03 % |
85.91 |
|
AMI MegaRAID IDE100, 1 Drive | 82.39 |
0.64 |
194.18 ms |
1.49 % |
55.30 |
|
Promise FastTrak 100, 1 Drive | 82.11 |
0.64 |
194.83 ms |
0.97 % |
84.65 |
| Load = Moderate |
|
Abit SL6, 1 Drive | 87.89 |
0.69 |
727.76 ms |
0.90 % |
97.66 |
|
Promise Ultra 66, 1 Drive | 99.85 |
0.78 |
640.55 ms |
1.14 % |
87.59 |
|
AMI MegaRAID IDE100, 1 Drive | 90.92 |
0.71 |
703.63 ms |
1.69 % |
53.80 |
|
Promise FastTrak 100, 1 Drive | 90.44 |
0.71 |
705.61 ms |
1.06 % |
85.32 |
| Load = Heavy |
|
Abit SL6, 1 Drive | 95.50 |
0.75 |
2647.68 ms |
1.49 % |
64.09 |
|
Promise Ultra 66, 1 Drive | 110.34 |
0.86 |
2316.28 ms |
1.66 % |
66.47 |
|
AMI MegaRAID IDE100, 1 Drive | 98.43 |
0.77 |
2596.53 ms |
2.21 % |
44.54 |
|
Promise FastTrak 100, 1 Drive | 98.16 |
0.77 |
2603.14 ms |
1.49 % |
65.88 |
|
|
|
| IOMeter Tests | IO/sec | MB/sec | Response Time | CPU Util. | IO/CPU% |
| Load = Linear |
|
Abit SL6, 1 Drive | 104.48 |
0.82 |
9.57 ms |
1.08 % |
96.74 |
|
Promise Ultra 66, 1 Drive | 105.25 |
0.82 |
9.50 ms |
1.17 % |
89.96 |
|
AMI MegaRAID IDE100, 1 Drive | 107.16 |
0.84 |
9.33 ms |
2.01 % |
53.31 |
|
Promise FastTrak 100, 1 Drive | 107.52 |
0.84 |
9.30 ms |
1.31 % |
82.08 |
| Load = Very Light |
|
Abit SL6, 1 Drive | 104.36 |
0.82 |
38.32 ms |
1.00 % |
104.36 |
|
Promise Ultra 66, 1 Drive | 105.17 |
0.82 |
38.03 ms |
1.13 % |
93.07 |
|
AMI MegaRAID IDE100, 1 Drive | 107.52 |
0.84 |
37.20 ms |
2.08 % |
51.69 |
|
Promise FastTrak 100, 1 Drive | 107.21 |
0.84 |
37.31 ms |
1.23 % |
87.16 |
| Load = Light |
|
Abit SL6, 1 Drive | 104.33 |
0.82 |
153.34 ms |
1.06 % |
98.42 |
|
Promise Ultra 66, 1 Drive | 105.12 |
0.82 |
152.17 ms |
1.09 % |
96.44 |
|
AMI MegaRAID IDE100, 1 Drive | 107.76 |
0.84 |
148.46 ms |
2.00 % |
53.88 |
|
Promise FastTrak 100, 1 Drive | 107.75 |
0.84 |
148.48 ms |
1.20 % |
89.79 |
| Load = Moderate |
|
Abit SL6, 1 Drive | 105.80 |
0.83 |
604.69 ms |
1.08 % |
97.96 |
|
Promise Ultra 66, 1 Drive | 106.68 |
0.83 |
599.56 ms |
1.23 % |
86.73 |
|
AMI MegaRAID IDE100, 1 Drive | 108.99 |
0.85 |
586.93 ms |
2.05 % |
53.17 |
|
Promise FastTrak 100, 1 Drive | 109.03 |
0.85 |
586.79 ms |
1.29 % |
84.52 |
| Load = Heavy |
|
Abit SL6, 1 Drive | 114.16 |
0.89 |
2239.30 ms |
1.71 % |
66.76 |
|
Promise Ultra 66, 1 Drive | 115.36 |
0.90 |
2215.46 ms |
1.68 % |
68.67 |
|
AMI MegaRAID IDE100, 1 Drive | 116.76 |
0.91 |
2189.30 ms |
2.70 % |
43.24 |
|
Promise FastTrak 100, 1 Drive | 116.70 |
0.91 |
2190.80 ms |
1.87 % |
62.41 |
|
|
|
| IOMeter Tests | IO/sec | MB/sec | Response Time | CPU Util. | IO/CPU% |
| Load = Linear |
|
Abit SL6, 1 Drive | 110.14 |
27.54 |
9.07 ms |
6.75 % |
16.32 |
|
Promise Ultra 66, 1 Drive | 110.39 |
27.60 |
9.05 ms |
3.56 % |
31.01 |
|
AMI MegaRAID IDE100, 1 Drive | 111.26 |
27.82 |
8.98 ms |
4.37 % |
25.46 |
|
Promise FastTrak 100, 1 Drive | 111.19 |
27.80 |
8.99 ms |
3.94 % |
28.22 |
| Load = Very Light |
|
Abit SL6, 1 Drive | 109.91 |
27.48 |
36.39 ms |
6.82 % |
16.12 |
|
Promise Ultra 66, 1 Drive | 110.51 |
27.63 |
36.19 ms |
3.74 % |
29.55 |
|
AMI MegaRAID IDE100, 1 Drive | 111.31 |
27.83 |
35.93 ms |
4.55 % |
24.46 |
|
Promise FastTrak 100, 1 Drive | 111.14 |
27.79 |
35.98 ms |
4.04 % |
27.51 |
| Load = Light |
|
Abit SL6, 1 Drive | 109.90 |
27.48 |
145.56 ms |
7.36 % |
14.93 |
|
Promise Ultra 66, 1 Drive | 110.55 |
27.64 |
144.71 ms |
3.92 % |
28.20 |
|
AMI MegaRAID IDE100, 1 Drive | 111.28 |
27.82 |
143.78 ms |
4.42 % |
25.18 |
|
Promise FastTrak 100, 1 Drive | 111.16 |
27.79 |
143.93 ms |
4.29 % |
25.91 |
| Load = Moderate |
|
Abit SL6, 1 Drive | 109.97 |
27.49 |
427.35 ms |
12.40 % |
8.87 |
|
Promise Ultra 66, 1 Drive | 110.50 |
27.62 |
579.16 ms |
6.13 % |
18.03 |
|
AMI MegaRAID IDE100, 1 Drive | 111.29 |
27.82 |
575.06 ms |
4.85 % |
22.95 |
|
Promise FastTrak 100, 1 Drive | 111.19 |
27.80 |
575.49 ms |
7.41 % |
15.01 |
| Load = Heavy |
|
Abit SL6, 1 Drive | 108.61 |
27.15 |
2126.35 ms |
11.58 % |
9.38 |
|
Promise Ultra 66, 1 Drive | 109.43 |
27.36 |
2115.21 ms |
5.65 % |
19.37 |
|
AMI MegaRAID IDE100, 1 Drive | 110.07 |
27.52 |
2121.00 ms |
5.52 % |
19.94 |
|
Promise FastTrak 100, 1 Drive | 110.07 |
27.52 |
2103.10 ms |
6.20 % |
17.75 |
|
|
The first thing one is likely to notice above is similarity between scores: there is no measurable performance difference whatsoever between these cards with a single drive. The MegaRAID's CPU utilization is again comes in somewhat higher, but it's nonetheless far too small of a difference to have any impact on performance.
RAID 0...
|
| IOMeter Tests | IO/sec | MB/sec | Response Time | CPU Util. | IO/CPU% |
| Load = Linear |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 71.52 |
0.77 |
13.98 ms |
1.40 % |
51.09 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 70.57 |
0.77 |
14.16 ms |
0.85 % |
83.02 |
| Load = Very Light |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 73.06 |
0.78 |
54.77 ms |
1.47 % |
49.70 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 71.83 |
0.78 |
55.68 ms |
0.94 % |
76.41 |
| Load = Light |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 84.00 |
0.92 |
190.43 ms |
1.74 % |
48.28 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 82.77 |
0.90 |
193.26 ms |
1.01 % |
81.95 |
| Load = Moderate |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 96.24 |
1.04 |
664.66 ms |
1.96 % |
49.10 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 94.87 |
1.02 |
674.39 ms |
1.29 % |
73.54 |
| Load = Heavy |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 109.76 |
1.19 |
2328.24 ms |
2.68 % |
40.96 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 108.14 |
1.18 |
2363.31 ms |
1.84 % |
58.77 |
|
|
|
| IOMeter Tests | IO/sec | MB/sec | Response Time | CPU Util. | IO/CPU% |
| Load = Linear |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 84.13 |
0.66 |
11.88 ms |
1.58 % |
53.25 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 84.16 |
0.66 |
11.88 ms |
1.05 % |
80.15 |
| Load = Very Light |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 85.35 |
0.67 |
46.86 ms |
1.56 % |
54.71 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 85.44 |
0.67 |
46.81 ms |
1.11 % |
76.97 |
| Load = Light |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 96.75 |
0.76 |
165.35 ms |
1.87 % |
51.74 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 96.49 |
0.75 |
165.77 ms |
1.22 % |
79.09 |
| Load = Moderate |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 110.39 |
0.86 |
579.55 ms |
2.31 % |
47.79 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 110.51 |
0.86 |
578.96 ms |
1.55 % |
71.30 |
| Load = Heavy |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 125.68 |
0.98 |
2034.28 ms |
3.03 % |
41.48 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 125.23 |
0.98 |
2041.51 ms |
2.10 % |
59.63 |
|
|
|
| IOMeter Tests | IO/sec | MB/sec | Response Time | CPU Util. | IO/CPU% |
| Load = Linear |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 81.59 |
0.64 |
12.25 ms |
1.64 % |
49.75 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 81.37 |
0.64 |
12.25 ms |
1.09 % |
74.65 |
| Load = Very Light |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 82.96 |
0.65 |
48.21 ms |
1.63 % |
50.90 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 82.37 |
0.64 |
48.55 ms |
1.00 % |
82.37 |
| Load = Light |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 93.29 |
0.73 |
171.47 ms |
1.74 % |
53.61 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 92.53 |
0.72 |
172.87 ms |
1.21 % |
76.47 |
| Load = Moderate |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 106.25 |
0.83 |
602.02 ms |
2.16 % |
49.19 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 105.36 |
0.82 |
606.88 ms |
1.45 % |
72.66 |
| Load = Heavy |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 120.71 |
0.94 |
2117.99 ms |
2.97 % |
40.64 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 121.28 |
0.95 |
2107.78 ms |
2.26 % |
53.66 |
|
|
|
| IOMeter Tests | IO/sec | MB/sec | Response Time | CPU Util. | IO/CPU% |
| Load = Linear |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 198.54 |
1.55 |
5.03 ms |
3.72 % |
53.37 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 196.79 |
1.54 |
5.08 ms |
2.50 % |
78.72 |
| Load = Very Light |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 198.92 |
1.55 |
20.10 ms |
3.57 % |
55.72 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 195.88 |
1.53 |
20.42 ms |
2.78 % |
70.46 |
| Load = Light |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 198.52 |
1.55 |
80.59 ms |
3.74 % |
53.08 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 196.34 |
1.53 |
81.47 ms |
2.80 % |
70.12 |
| Load = Moderate |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 200.29 |
1.56 |
319.44 ms |
4.14 % |
48.38 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 197.14 |
1.54 |
324.54 ms |
2.88 % |
68.45 |
| Load = Heavy |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 208.17 |
1.63 |
1228.70 ms |
5.11 % |
40.74 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 205.58 |
1.61 |
1243.42 ms |
4.02 % |
51.14 |
|
|
|
| IOMeter Tests | IO/sec | MB/sec | Response Time | CPU Util. | IO/CPU% |
| Load = Linear |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 222.67 |
55.67 |
4.49 ms |
10.85 % |
20.52 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 221.57 |
55.39 |
4.51 ms |
7.93 % |
27.94 |
| Load = Very Light |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 222.63 |
55.66 |
17.96 ms |
11.12 % |
20.02 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 221.68 |
55.42 |
18.04 ms |
8.32 % |
26.64 |
| Load = Light |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 222.75 |
55.69 |
71.82 ms |
10.91 % |
20.42 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 221.49 |
55.37 |
72.23 ms |
8.73 % |
25.37 |
| Load = Moderate |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 222.65 |
55.66 |
287.43 ms |
12.03 % |
18.51 |
|
Promise FastTrak 100, RAID 0, 2 Drives | 221.58 |
55.40 |
288.78 ms |
12.35 % |
17.94 |
| Load = Heavy |
|
AMI MegaRAID IDE100, RAID 0, 2 Drives | 219.90 |
54.98 | |
|
| |