Using the i-RAM

To begin our testing, we loaded up the i-RAM with four 1GB DDR400 sticks.  We didn't have any large DDR200 modules, so unfortunately we had to go with more modern DDR400.  Using DDR500, DDR400 or DDR200 doesn't change performance at all, since the Xilinx controller runs them all at the same frequency. 

With all four banks populated, we connected the i-RAM to our ASUS A8N-SLI Deluxe with a regular SATA cable and plugged the card into an open PCI slot. 

Powering the system on revealed the installation was a success; the BIOS reported the presence of the i-RAM as a regular storage device connected to our SATA controller:

Before Windows would recognize the drive, we had to create a partition on it, the same way you would a hard drive that had no partition on it initially.

After doing so, the i-RAM was completely functional as a regular hard drive:

The biggest difference that you notice with the i-RAM isn't necessarily its speed, but rather its sound - it's silent.  There are no moving parts, it's silent when the drive is accessed and it obviously doesn't have to spin up or down when the computer starts up.  These are all very obvious elements of the card, but they don't really sink in until you actually begin using it. 

Also, all disk accesses are instantaneous; formatting the thing takes no time at all, and you can even "defragment" it (although, you get no benefit from doing so).

With the setup done, it was time to evaluate the i-RAM as more than just a novelty silent  hard drive.  Armed with our 4GB partition, we started testing...

The Test

We ran all of our tests on the following testbed unless otherwise noted:

ASUS A8N SLI Deluxe nForce4 SLI Motherboard
AMD Athlon 64 FX-57 Processor
1 GB OCZ 2:2:2:7 DDR400 RAM
Seagate 7200.7 120 GB Hard Drive (boot drive)
Western Digital Raptor W740GD (test drive)
Gigabyte i-RAM w/ 4x1GB DDR400 modules (test drive)

We used the latest nForce 6.53 and ForceWare 77.72 drivers for our test bed, and paired it with the recently released GeForce 7800 GTX.

i-RAM’s Limitations i-RAM Pure I/O Performance
Comments Locked

133 Comments

View All Comments

  • Sea Shadow - Monday, July 25, 2005 - link

    I wonder if the OS is the limiting factor. They should run some tests using other os *cough* linux *cough*.

    What would be really neat is if they could design an i-Ram device that uses 2 HDD bays and supported 8+ GB of ram and ran from a standard molex.
  • sprockkets - Tuesday, July 26, 2005 - link

    You people think about using Knoppix and copying to the drive? For that matter, that and stuff like damnsmalllinux and such can be run totally from system ram.

    Instead of using this though for a slient drive, you are better off using flash memory drives for that.
  • ViRGE - Monday, July 25, 2005 - link

    Unfortunately if they did that, it would mean that your computer could never be turned off. As noted in the review, the card is currently still powered even if the machine is "off", due to the fact that when a modern ATX computer is off, it's actually more of a super-standby mode that leaves a few choice items powered on for wake-on events(LAN/modems, and the power button of course). All Gigabyte is doing here is taping in to the 3.3v line on the PCI slot that wake-on power is provided through, which is enough to keep the device powered up even when the system is in its diminished state.

    Molex plugs on the other hand are completely powered down when the system is "off", so it would be running off of battery power in this case. A lot of us leave our systems on 24/7 anyhow, but I still think they'd have a hard time selling a device that would require your computer to be off for no more than 16 hours at a time.
  • Gatak - Monday, July 25, 2005 - link

    They could use the USB power. On most motherboards you can enable with a jumper or BIOS to supply standby power to the USB. Often the setting is called "Wake on USB" or "Wake on Keyboard" etc
  • reactor - Monday, July 25, 2005 - link

    "What would be really neat is if they could design an i-Ram device that uses 2 HDD bays and supported 8+ GB of ram and ran from a standard molex."

    Was thinking something similar myself as i was reading.

    I think once ram modules are 4gb or larger, then this could be very useful. But not until it gets updated with sata2, ddr400 etc. When the time comes to build an HTPC then ill give this another look.

    Nice article.
  • ranger203 - Monday, July 25, 2005 - link

    Not to shabby, but i was honestly expecting like 3 second boots, & 5 second game load times... why is there only a 20% speed increase in some areas?
  • Griswold - Thursday, July 28, 2005 - link

    Because the data still has to be processed after being loaded - bandwith is obviously not the biggest bottleneck here.
  • forwhom - Tuesday, July 26, 2005 - link

    What I would be very interested in seeing is the performance of the thing using it as the source for encoding a dvd/mpeg... Most encoders are heavily disk-based and if it could reduce the time significantly it might be worth while - assuming that eventually they come out with one big enough to hold the source. There's now reasonable CPU encode performance, just have to get the data to/from it... maybe the i-drive would help..
  • highlandsun - Monday, July 25, 2005 - link

    Hmmm, the WD Raptor has a sustained transfer rate of 72MB/sec. So on a freshly formatted drive, with no fragmentation, it should still be half the speed of the iRam. But at $200 for a 74GB drive, then you could get a pair of these running in RAID0, which would run at around 140MB/sec anyway, and still have spent less than the cost of the iRam and 4GB of DDR DIMMs. It definitely seems like this product falls short.

    The use of PCI 3.3V standby power is clever. Perhaps a future version should just use a dummy PCI card to provide the power, connected to a 5" drive-size case with many more DIMM slots. If you can't cram at least 16 DIMMs in there, then the ability to use old memory is kind of wasted, since the old modules will have such small capacities.

    Ultimately I think this type of product will always be a failure.

    What they should do instead is make it a pass-through cache for a real SATA drive. So you plug the SATA controller into it, and plug it into a real SATA drive, and it caches all I/O operations to the real drive. That's the only way that you can get meaningful benefit out of only 4GB of memory. A card like this would turn any SATA drive into a speed demon; 4GB is definitely a decent size for most caching purposes.
  • highlandsun - Monday, July 25, 2005 - link

    Of course the next logical step is to put the DIMM slots on the SATA controller card, so that access to cached data occurs at real memory speeds, not just SATA bus speed. This would only be a useful product for folks stuck on 32-bit systems, because otherwise it would be best to just increase the system memory instead. But there are plenty of 32-bit systems out there that would benefit from the approach.

Log in

Don't have an account? Sign up now