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

  • NStriker - Thursday, July 28, 2005 - link

    Anand quotes $90 per GB of RAM here, but I'm wondering if the I-Ram works with the much cheaper high-density junk you see out there all the time. Like 128Mx4 modules. On motherboards, usually only SiS chipsets can handle that type of RAM, but there's no reason the Xilinx FPGA couldn't.

    Right now I'm seeing 1GB of that stuff for $63.
  • jonsin - Thursday, July 28, 2005 - link

    Since Athlon64 north bridge no need the memory controller. Why shouldn't the original memory controller used for iRam purpose. By supporting both SDRam and DDR Ram, people can make use of their old RAM (which no longer useful nowadays) and make it as Physical Ram Drive.

    Spare some space for additional DDR module slot on motherboard exclusively for iRam, and additional daughter card can be added for even more Slots.

    Would it be a cheaper solution for iRam ultimately ?
  • jonsin - Thursday, July 28, 2005 - link

    And more, power can be directly drive from ATA power in motherboard. By implementing similar approach to iRam, an extra battery can power the ram for certain hours.

    By enabling north bridge to be DDR/SDRam capability is not a new technology, every chipset compnay have such tech. They can just stick the original memory controller with lower performance (DDR200, so more moudle can be supported and lower cost) to north bridge, the cost overhead is relatively small.

    What I think the extra cost comes from extra motherboard layout, north bridge die size, chipset packaging cost (more pins). I suppose it can cost as low as $20 ?
  • jonsin - Thursday, July 28, 2005 - link

    More, the original SATA physical link can be omitted as the controller in North Bridge can communicate directory to SATA controller internally (South bridge thru HT ?) In this case, would the performance increate considerably and the overall layout more tidy ? (no need external cable and cards)
  • mindless1 - Friday, July 29, 2005 - link

    NO these are all problems. The purpose is to have a universal platform support that is gentle on power consumption. That means a tailored controller and even then we're seeing the main limit is the battery. "Tidy" is an unimportant human desire, particularly less important inside a closed PC case. All they have to do is route bus traces well on the card and be done.
  • slumbuk - Wednesday, July 27, 2005 - link

    HP sell an add on for their DL 380 server for $200 (at discount) that gets you 128MB of disk write cache... makes a good system also fast for disk writes.

    This card could be used by linux vendors to enable file-system data and control logging for similar money for GB(s) of write cache... Cheap, reliable, fast general purpose file servers.. that have fast disk write speed without risking data loss.. Speed meaning no disk-head latency, no rotational latency - just transfer time.

    It would sell better with ECC memory.. or the ability to use two cards in a mirror.. at least to careful server buyers..

  • slumbuk - Wednesday, July 27, 2005 - link

    You could set up the iRam drive as the journal device for Resier or Ext-3 logged file systems - and log both control info and data - for fast, safe systems without too much fuss.

    I think I want one - but not as much as I want other stuff..
  • AtaStrumf - Wednesday, July 27, 2005 - link

    Interesting but hardly useful for most. Kind of makes sense to only make 1000, but of course that's where the $150 price tag comes from.
  • rbabiak - Wednesday, July 27, 2005 - link

    i guess it would add to the base board cost, but a SATA controller on the PCI card would make it a littl nicer as then you are not takeing up one of your SATA channels, i only have 2 and they are current both used for a Raid-0

    Also if they made the PCI card a SATA interface and then short circeted the backend to conect directly to the memory, wouldn't they then be able to get much higher transfer speeds than sata and yet all the existint SATA divers could be used with it, given they emulate a existing SATA interface.
  • DerekWilson - Thursday, July 28, 2005 - link

    Better to use the onboard ports ...

    a 33MHz/32bit PCI slot only grants a max of 133MB/sec. This would make the PCI bus a limiting factor to the SATA controller.

    Step beyond that and remember that the PCI bus is shared among all your PCI cards. Depending on the motherboard some onboard devices can be built onto the PCI bus.

    With bandwidth on current southbridge chips already being dedicated to SATA (or SATA-II), it would be a waste in more ways than one to build a SATA controller into the i-RAM.

    That's my take on it anyway.

    Derek Wilson

Log in

Don't have an account? Sign up now