Gigabyte's i-RAM: Affordable Solid State Storage
by Anand Lal Shimpi on July 25, 2005 3:50 PM EST- Posted in
- Storage
i-RAM as a boot drive
Since the i-RAM appears as a normal hard drive, you can install Windows on it just like you would a regular hard drive with no extra drivers (assuming that none are needed for your SATA controller).A full install of Windows XP Pro can easily fit on a 4GB i-RAM and even on a 2GB i-RAM, but you have to be careful not to install applications into the C:\Program Files directory and disable System Restore for the i-RAM drive among other precautions. Why would you ever want to install your OS on an i-RAM card? We came up with two possibilities:
First off, loading your OS on the i-RAM will reduce boot times.
| Boot Time Comparison | |||||
Windows Boot Time (Lower is Better) |
|||||
| Gigabyte i-RAM (4GB) | 9.12s |
||||
| Western Digital Raptor (74GB) | 14.06s |
||||
With a Western Digital Raptor, you can go from the boot menu to the Windows desktop in 14.06 seconds; with the i-RAM, it takes 9.12 seconds. It's not instantaneous, but it's definitely quicker and noticeable.
Our thoughts are that with further optimization, the boot process can be better tuned for very low latency storage devices such as the i-RAM, but that won't happen with any currently shipping version of Windows.
The second reason for installing your OS on an i-RAM card is a bit more specific, but one we came up with when thinking about a secondary benefit of Gigabyte's i-RAM: it's silent.
You could theoretically build a home theater computer using just the i-RAM to hold your OS and map a network drive (hopefully kept in another room) to hold all of your media (e.g. music, movies, pictures, etc.). Paired with a silent PSU and a very quiet running CPU fan (maybe even on a Pentium M based system), you can have a truly silent HTPC, thanks to the i-RAM. You'd ideally want whatever database of your media collection to be stored on the network drive and not your OS, just in case something ever happened causing your i-RAM to lose its data, but it is a viable use for Gigabyte's i-RAM.
Facebook
Twitter
RSS
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-0Also 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