i-RAM for Gamers

Although you definitely need more memory if your game is pausing during gameplay to swap to disk, level load times can be very annoying, especially with the excruciatingly long load times of some recent popular titles such as Unreal Tournament 2004 and Battlefield 2. So, what about using the i-RAM as a "game drive" to store whatever game you happen to be playing the most at the time, and hopefully reduce those pesky load times?

So, we went to test a handful of games, Splinter Cell 3, Doom 3, Battlefield 2 and UT2004, and in that quest, we ran into our first problem - UT2004 required around 5GB of space to install, and we only had 4GB on our i-RAM. The rest of our tests proceeded without a problem, but the capacity issue is one that was an underlying theme of our testing with the i-RAM: its Achilles' heel is its capacity limitation more than anything else.

Most of the games that we installed on the i-RAM occupied between 1GB and 3.5GB of space, but we wouldn't put it past many developers to begin pushing those limits very soon, if they aren't already. But then again, you could always add another i-RAM later, so how'd it fare in the games we could install on it?

Game Level Load Time Comparison (Lower is Better)
Splinter Cell: CT
Doom 3
Battlefield 2
Gigabyte i-RAM (4GB)
8.0s
19.6s
20.83s
Western Digital Raptor (74GB)
10.59s
25.78s
25.67s

First off, we had Splinter Cell 3 - we ran the lighthouse benchmark that ships with the game and timed the loading screen for the level. The Raptor came in at just under 11 seconds, while the i-RAM came in at 8 seconds. Not a huge improvement, and honestly not overly noticeable (other than the fact that there was no disk crunching), but it was a measurable difference.

Doom 3 proved to be a bit more appreciative of the i-RAM's efforts; the Raptor came in at just under 26 seconds, while the i-RAM loaded the first level in 19.6 seconds. Again, if you were expecting the load time to drop to instantaneous, that's not going to happen, but the reduction in this case was quite measurable.

Our final test was the big one - Battlefield 2. For this test, we used our benchmark level and once again, timed the ever-so-long loading screen. The Raptor got us out of that screen in 25.67 seconds, and the i-RAM did it in 20.83 - a similar performance gain to what we saw in Doom 3.

Overall, we saw some reasonably tangible performance improvements in game level load times - but nothing we would characterize as spectacular. For the money, you're much better off buying a better video card to improve your gaming performance; but if you happen to already own a pair of GeForce 7800 GTXes, then maybe an i-RAM is in your future.

i-RAM as a boot drive i-RAM for Applications
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