i-RAM as a Paging Drive

One question that we've seen a lot is whether or not the i-RAM can be used to store your pagefile. Since the i-RAM behaves just like a regular hard drive, Windows has no problem using it to store your pagefile, so the "can you" part of that question is easily answered. The real question happens to be, "should you?"

We have heard arguments on both sides of the fence; some say that Windows inefficiently handles memory and inevitably pages to disk even when you have memory to spare, while others say that you'd be stupid to put your pagefile on an i-RAM rather than just add more memory to your system. So, which is it?

Unfortunately, this is the type of thing that's difficult to benchmark, but it is the type of thing that's pretty easy to explain if you just sit down and use the product. We set up a machine, very similar to how we would a personal system, but tended to focus on memory hogs - web pages with lots of Flash, Photoshop, etc. Of course, we opened them all up at once, switched between the applications, used them independently, simultaneously, basically whatever we could do to stress the system as it normally would be stressed.

At the same time, we monitored a number of things going on - mainly the size of the pagefile, the amount of system memory used, the frequency of disk accesses, pagefile usage per process... basically everything we could get our hands on through perfmon to give us an idea if Windows was swapping to disk or not.

The end result? There was no real tangible performance difference between putting more memory in the system and using the hard disk for the pagefile or putting less memory in the system and using the i-RAM for the pagefile. Granted, if we had a way of measuring the overall performance, it would have shown that we would be much better off with more memory in the system (it runs faster, and it is accessed much quicker than off the i-RAM).

The only benefit that we found to using the i-RAM to store our pagefile was if you happened to have a couple GBs of older DDR200 memory lying around; that memory would be useless as your main system memory in a modern machine, but it'd make a lot better of a pagefile than a mechanical hard disk.

One more situation we encountered that would benefit from storing your pagefile on the i-RAM was those seemingly random times when Windows swaps to disk for no reason. But for the most part, our system was slower when we had less memory and stored the swapfile in it than when we had more memory and less swap file.

Adobe Photoshop is a slightly different creature as it keeps a scratch disk that is separate from the Windows pagefile. We tested Photoshop and used the i-RAM as our scratch disk, but in all cases it always made more sense to just throw more memory at Photoshop to improve performance where we ran out of memory. If the operations you're performing in Photoshop can fit into system memory, then you'll never touch the scratch disk.

Overall, based on our testing, the i-RAM doesn't make much sense as a paging drive unless you have the spare memory. The problem with "spare" DDR200 memory is that it is most likely in small 64MB, 128MB or maybe 256MB sizes, which doesn't buy you much space on an i-RAM drive. For most people, you're much better off just tossing more memory in your system.

i-RAM Pure I/O Performance i-RAM as a boot drive


View All Comments

  • - Tuesday, July 26, 2005 - link

    I was really surprised at how little it helped as a page file. Myself I sometimes encounter periods of slowdown due to paging that can last for several minutes where nothing can be done. I don't know if there's a common name for this but I'll call it the "page file wall". I don't know exactly how you would recreate such a tragedy in the lab. Too many apps open with too little memory obviously. But less obviously, it seems that during a period of overnight inactivity (with apps left open) windows will page a lot of stuff out to disk and you can experience the page file wall the next morning. It'd be interesting if Anand could devise a consistent "page file wall" benchmark.

    As the article and many posts above suggest doubling my RAM would probably end my problems.

    I still think this product (or revision 2 or 3) could bridge an obvious gap with PC's: SLOW harddisks and EXPENSIVE ram. When you run out of ram it can be like hitting a wall. It can be like crossing the country, but you go half by jet and the other half on foot. The gap should be filled with something cheaper than modern DDR and faster than harddisks. (This product is barely either.) I'd like to see a PC with 1 GB normal ram and 2GB of cheap-o 1/8 speed auxiliary ram. The OS could use this slower ram for paging with priority over paging to the harddisk. Not just for enthusiasts, but for regular beige PC's. Owners would then have another upgrade option with a better cost/benefit ratio depending on their needs.

    I was waiting for a performance review of this thing and I'm so glad trusty Anandtech provided.

    BTW: Long time reader (4+years), 1st time poster.
  • - Tuesday, July 26, 2005 - link

    I was in my local computer shop and the guy working there pointed at a stack of hardware and said some guy just dropped $8000 on a Intel 955X or whatever system that included around 16 gigs of Ram disks and I asked if it was based on ddr400 and he said no it was in fact ddr2 533 I think. A quick search on the internet found nothing about ddr2 ram drives and it defies logic to me anyway since i would think that ddr 400 would be faster due to latency issues, etc. Has anyone heard anything like this? Also the guy at the store told me that it boots in to Windows XP in 4 seconds. It sounds like a tall tale but i don't see any reason why he would be making it up as they are pretty reputable. Reply
  • davidlang - Tuesday, July 26, 2005 - link

    where you really suffer is on writes.

    any time you need to write something before you can continue the latency becomes critical. Database writes (and logging) are a perfect example of this.

    Under *nix the Journal of a journaling filesystem is performance critical (although it's useually a sequential write so it is about as good as you can get.

    For Database engines that have good crash recovery (MySQL is not that good at this, but Postgres or Oracle are) they need to make sure that their log gets to a safe storage media before they can consider the write completed and tell the caller that it's done.

    even for an apache webserver, with normal logging apache will not return the page until the log has been written.
  • somu - Tuesday, July 26, 2005 - link

    As a lot of ppl have posted here, it would make sense to use this as a cache for our harddrives by making it possible to plug the harddrive into the i-ram and i-ram to the motherboard. This would overcome the 4gb limitation and we probably wouldnt need the full 4gb for cache we can use like 1gb or 2 gb. But to see more increase in performance they will need to move it to sata2 and have programmers write into their code to precache data to take full advantage of the i-ram. Reply
  • AngleRider - Tuesday, July 26, 2005 - link

    Well it seems that modern hard drives are getting alot faster and solid state doesn't seem to help as much as it would of say, 2 or 4 years ago when we were running crusty low density HDs...

    However, I am also slighty disappointed in the design...

    Why put main system memory in a drive and then limit it to SATA I (not SATA2)?
    I thought the whole point of a ram drive was provide maximum i/o performance...??

    Second not allowing 2GB sticks doesn't make sense to me... i mean 4gb is really small.
    Maybe they should of thought this,
    "Gee, let's try to offer more capacity - like, golly bunny, currently available 2gb ram modules..."

    Even so, if this can do 591% higher i/o performance than a raptor in ipeak business winstone, then i'm sure there are ways to utilize this in computing tasks...
    Also if u put the os on it u wont ever need to defrag...

    Nice, but expensive for now ... expensive doesn't mean its crap.. just weakly spec'd to my mind for now...
    Why do something like this and then water it down?


  • UNCjigga - Tuesday, July 26, 2005 - link

    I think the disappointing benchmarks ought to say something about current OS's suitability to the iRAM, and not iRAM's capabilities. I really think this is an idea ahead of its time. Windows XP isn't tuned for solid-state storage, the FPGA chip on the iRAM isn't the best solution, and the SATA interface itself is a bottleneck. If Windows Vista and future BIOSes had support for PCIe storage, imagine a version of iRAM that had a straight PCIe interface supporting the full 1.6Gb/s or more depending on the type of memory you put on, and 8Gb or more memory thanks to 64bit addressing.

    Windows Vista will already have support for hybrid drives (NAND+platter) so the caching and paging routines will be optimized for solid-state storage. I actually think iRAM might be better than hybrid drives because 1) you can use existing drives with it, 2) iRAM is expandable (up to a limit), 3) DDR is faster than NAND
  • shaw - Tuesday, July 26, 2005 - link

    I could see SATA II could remove the bottleneck, but still, 4GB of data? Gigabyte is smarter then this.. it's just not going to fly. Though, it is a pretty good start.

    The next logical steps is probably finding a way to get a standard harddrive to use something like this as a memory buffer (7200rpm with DDR200 1GB of cache) and then maybe it would actaully be worth it.
  • JNo - Tuesday, July 26, 2005 - link

    I was disappointed that nothing was mentioned of the practicalities of moving windows or a game onto this thing. Is there any software that would transfer whatever data is on this thing (including functioning operating systems) to a normal drive at regular intervals? And keep them functioning? If not, what's the point?! Each time you have to install windows/a game to this thing (after powerfailures or just for the sake of having something different on it), you have to install all the updates/personal tweaks/mods/saved games/configurations etc which would takes SO MUCH MORE TIME than the extra few seconds you save from faster boot/game load times... why anandtech does not take these things into consideration?! To paraphrase another poster: WHOOPEE-F*CKING-DO Reply
  • araczynski - Tuesday, July 26, 2005 - link

    disappointing gaming benefits, too small a size, they should've used a custom controller rather then the connect-the-dots one.

    i'll be waiting to see what version 3 brings.
  • EODetroit - Tuesday, July 26, 2005 - link

    The $150 thing is a killer. But if they can only pump out 1000 of them, it makes business sense to have the price high. This just like AMD having high X2 prices because they can't possibly make enough quantity to fill orders if the price was lower... same exact thing.

    $90 per 1GB stick of ram is high, I'm sure people can shop around and find it cheaper.

    As for RAIDing two of these, Anand said he only actually had one of them, but was trying to get a second. So maybe more on that later. I think that even if Raid 0 doesn't work for some reason, JBOD would work.

    I'm curious what the bottleneck in computers now-a-days really is. I think Anand should get an NForce Pro with 8 GB of ram running 64bit XP, set up the largest RAM DISK (real software-type RAM disk) you can, and see how that affects performance. If performance shows the same mediocre gains that this device showed, then that means a new SATA2 version wouldn't improve things either. If that test showed there were large gains out there to be had, then yeah there's a future here. I would do it myself but I don't have access to that hardware hehe.

Log in

Don't have an account? Sign up now