Final Words

Armed with four 1GB sticks, we ran into more than a few cases where the i-RAM's size limitations made it impractical for use in our system.  Although 4GB is enough for a good deal of applications, an 8GB card would get far more use.  Based on the size of applications and games that we tried installing on the card, we'd say that 8GB would be the sweet spot - which unfortunately would either take two cards or much more expensive DIMMs.  We wouldn't recommend going with a 2GB partition unless you have a very specific usage model that you know won't use any more.  With only 2GB, we quickly found ourselves very constrained for space.  The past few years of having much more storage than we could ever ask for has unfortunately made us forget about how tough things can get with only a couple of GBs of space. 

Although the card is presently cramped with just four DIMM slots, one option for Gigabyte is to introduce a two-slot version with support for eight DIMMs.  The problem that we foresee most people running into is that older memory may be plentiful, but is usually smaller in size.  By the time current Athlon 64 users migrate to DDR2, they may have a handful of 512MB or 1GB sticks laying around, but presently, the only spare memory that you're most likely to have is a few 128MB or 256MB DDR modules from older builds.  Without being able to re-use older memory, the cost of outfitting an i-RAM card with a full 4GB of memory starts getting expensive.  At $90 per gigabyte of memory, you're talking about $360 just in memory costs, plus another $150 for the card itself.  For most folks, that's a pretty steep entry fee, but then again, if you've just splurged on a GeForce 7800 GTX, then maybe your budget can handle it. 

But that right there hits the nail on the head; by no means is the i-RAM a cheap upgrade, but then again, neither is an Athlon 64 X2, or a brand new 7800 GTX, or an SLI motherboard.  If you put it in perspective, an i-RAM with 4GB of brand new DDR400 memory isn't all that expensive compared to some of the other upgrades that we've recommended recently.  So the question then becomes, is Gigabyte's i-RAM as important to your overall system performance as an Athlon 64 X2 or a GeForce 7800 GTX?

For gamers, there is a slight improvement in level load times if you keep your game on the i-RAM.  Most games will fit on a 4GB card, but as we noticed during our testing, not all will.  The reduction in load times isn't nearly as dramatic as we had originally thought. It seems as if level load times are actually more affected by CPU and platform performance than just disk performance. 

Those users who have one or two applications that occupy all of their time, and tend to take a while to load or work with due to constant disk access would be more than happy with the i-RAM.  By far, the biggest performance improvements we saw when using the i-RAM were obviously with disk intensive operations such as file copying.  If your applications or usage models involve a lot of data movement without much manipulation, then the i-RAM may very well be what you need. 

At the same time, for all of the situations where the i-RAM was quite useful, there were a number where it wasn't.  Multitasking performance went up, but only in one out of the three Winstone tests, and even then, it's going to be rather tough to install a large number of applications on the i-RAM due to its size limitations, so your multitasking performance benefits will be numbered.  Game load times weren't always improved by a great deal and as we saw with the Business and Multimedia Content Creation Winstone tests, sometimes you are better off with a faster CPU than with the i-RAM. 

The important thing to focus on is that thanks to Gigabyte's battery system, data-loss was never an issue during our use of the card; and despite the lack of ECC memory support, we never had any data corruption during our testing. 

In the end, the i-RAM is an interesting addition to a system, but it's usefulness will truly vary from one user to the next.  With a bit more capacity, and especially for those users who happen to have a few 1GB sticks laying around, the i-RAM could be a very powerful addition to your system. Hats off to Gigabyte for making something useful, and we can't wait to see rev 2...

Overall Performance
Comments Locked

133 Comments

View All Comments

  • Hacp - Monday, July 25, 2005 - link

    It could be useful for pagefile if you have a couple of old 128-256 DDR 333 or older sticks lying around, especially if your ram slots are filled with 4x 512. This can defenetly improve performance over the hard drive pagefiling, which is horrible. I wish Gigabyte would have done 8 sticks instead of 4. The benefit of 8 sticks is that it will allow users to truley use their old sticks of ram 128,256, etc instead of just 1GB sticks. Right now, the price is too high for the actual I-ram module, and also the price of ddr ram is too much. If Gigabye does this right, they could have a hit, but it does not look like they are moving in the right direction. IMO, 2x or 3x Irams with cheap 512 and 256 sticks of old ram running in a raid onfiguration would be an good solution to the hard drive bottleneck, especially if people these days are willing to pay a premium for the Raptors.

    Also, nice article Anand!
  • zhena - Monday, July 25, 2005 - link

    mattsaccount you would need 3 cards to run raid 5.

    Here is one thing that is not mentioned on anandtech in most of the storage reviews, and that is responsiveness (as i like to call it.) Back early in the day when people were starting to use raid 0, most benchmarks showed little improvement in overall system performance, even now the difference between a WD raptor and a 7200rpm drive is little in terms of overall system performance. However most benchmarks don’t reflect how responsive your computer is, it's very hard to put a number on that. When I setup raid 0 back in the day, I noticed a huge improvement while using my computer, but I am sure that the actual boot time didn't increase much. Something with the i-ram card, using it probably feels a lot snappier than using any hard drive, which is very important.
  • ss284 - Monday, July 25, 2005 - link

    Raid 0 has a higher access time than no raid. Unless you were running highly disk intensive applications the snappiness would be attributed to ram, not the harddrive.

    -Steve
  • zhena - Monday, July 25, 2005 - link

    not at all steve, the access time goes down .5ms at most (don't take my word for it i've tested it with many benchmarks) but raid 0 shines where you need to get small amounts of data fast. if you are looking for a mb of data you get it twice as fast as from a regular harddrive, (assuming around 128k raid blocks). And due to the way regular applications are written and due to locality of reference, thats where responsiveness feel comes from.
  • JarredWalton - Monday, July 25, 2005 - link

    RAID 0 would not improve access times. What you generally end up with is two HDDs with the same base access time that now have to both seek to the same area - i.e. you're looking for blocks 15230-15560, which are striped across both drives. Where RAID 0 really offers better performance is when you need access to a large amount of data quickly, i.e. reading a 200MB file from the array. If the array isn't fragmented, then RAID 0 would be nearly twice as fast, since you get both drives putting out their sequential transfer rate.

    RAID 1 can improve access times in theory (if the controller supports it) because only one of the drives needs to get to the requested data. If the controller has enough knowledge, it can tell the drive with the closer head position to get the data. Unfortunately, that level of knowledge rarely exists. You could then just have both drives try to get each piece of data, and whichever gets it first wins. Then your average rotational latency should be reduced from 1/2 a rotation to 1/4 a rotation (assuming the heads start at the same distance from the desired track). The reality is that RAID really doesn't help much other than for Redundancy and/or heavy server loads with a high-end controller.
  • Gatak - Monday, July 25, 2005 - link

    Um yes. This is what I meant - mirroring (raid1, not raid0) would increase access times as both disks could access different data independently (if the controller was smart). Sorry about the confusion.
  • ss284 - Tuesday, July 26, 2005 - link

    I was reffering to raid 0 in my post if you didnt notice. There is no way RAID-0 would lower access times. Its impossible seeing as the data is spanned accross both drives, meaning the seek would be no faster than a single drive, and likely a tiny bit slower because of overhead.
  • Gatak - Monday, July 25, 2005 - link

    RAID-0 ought to offer better random read access times as there are two disks that can read independently. Writing would be somewhat slower though as both disks need to be synced.
  • Gatak - Monday, July 25, 2005 - link

    I'd like to see some server benchmarks with this. For example:

    * mail server (especially servers using maildir is generating lots and lots of files)
    * web server
    * file server
    * database server (mysql, for example)

    Maybe some other benchmarks :D
  • mmp121 - Monday, July 25, 2005 - link


    He even states that on page 11:

    quote:

    One of the biggest advantages of the i-RAM is its random access performance, which comes into play particularly in multitasking scenarios where there are a lot of disk accesses.


    Anand, how about an update with some server / database benchies?

    Gigabyte might have something on its hands if it makes the card SATA-II to use the speed of the RAM. 1.6GB/s through a 150MB/s straw is not good. Anyhow, here's looking forward to REV 2.0 of the i-RAM GigaByte!

Log in

Don't have an account? Sign up now