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

  • abzzeus - Tuesday, July 26, 2005 - link


    This a a 4GB PCI Drive @$3000 (yes three thousand) but this is for a native drive with direct access to the PCI bus thus can sustain 133Mbit/s.

    What I'd like to see is a version that fits in 5.25" drive slot 12+ slots for RAM using a std connector for power and SATA II or SCSI (SCA?).

    I can see several advantages for this product IF you think about it
    Webcache server (hold the cache)
    Temporary files (great for those programs that write temp files like crazy)
    Swap space on Database server (lookup PAE, SQL server and 36bit addressing - 32bit windows can address upto 8GB RAM IF the O/S and the app are writen for it (been there :( )
    Swap space on badly behaved app - there are apps that are ported from *nix to windows that tell the OS I have pagable RAM which the server then dumps to disc (4million page faults in 2 hours!) only for the app to ask for it
    Log files - DB servers write out transitional logs once per transaction, this needs a drive that is FAST

    Having more than one of these in a system (power system) means that you can seperate out the I/O onto seperate physical drives or even better controller or best seperate PCI buses (Servers, Really big servers can have three PCI buses) this means for a server (Unit means logical disc made from RAID arrays, seperated out as much as possible, by controller and PCI bus)

    Unit 1 - OS and Apps Binaries
    Unit 2 - Paging file
    Unit 3 - Logs
    Unit 4 - Temp
    Unit 5 - Data

    Maximum seperation equeals maximum I/O

  • Klober - Tuesday, July 26, 2005 - link

    First off, another good article Anand. Now, on to my point...

    I'm wondering about World of Warcraft. After the first article where the info debuted there was a lot of talk in the comments section, and one of the subjects was WoW. It wouldn't have been possible to install WoW to the i-RAM because it's too big (~4.6GB on my machine). However, once AnandTech recieves another i-RAM to test with, either in JBOD or RAID-0, I would like to hear at least a subjective opinion on how WoW runs in large battles and such. I know my brother's machine gets stuttery when there's a big PvP battle, and through my troubleshooting I've gathered that it's a hard drive speed issue. If any of the AnandTech team has a high level character on their account and like PvP, please post something on performance in WoW.

  • JarredWalton - Tuesday, July 26, 2005 - link

    I can't see having the i-RAM as being more beneficial to any game than simply adding more RAM to the system. If you're going to have 4x1GB DIMMs installed on the i-RAM, why not just put them into the system itself instead? As for WoW, even if the installed size is 4.6 GB, I doubt the game actually goes much above 1GB of memory use - very few applications do. If you have 2GB or more of RAM, do you still get stuttering issues in WoW? If so, there's a reasonable chance that it's simply GPU power that's lacking rather than RAM - or perhaps GPU RAM would help?

    (Note: I'm not a WoW player, so I'm just shooting from the hip.)
  • EODetroit - Wednesday, July 27, 2005 - link

    There are at least 3 seperate data files in the WoW installation that are 1 GB in size each. A bunch of smaller but still over 100 MB files as well. All told as he said its about 4.6GB, and its more than 4GB in that one folder alone. So yeah, the game would go over 1GB in memory use if it was written well enough.

    I play WoW a lot, and loading into highly populated areas sucks. You hard drive thrashes and you have no control of your character until everything is loaded. I'm assuming its busy loading the textures of the equipment that all the player charactes around you are wearing.

    This I-Ram thing might help out a lot, seeing as consumer motherboards don't support over 4GB of memory and the data files alone for WoW totals over 4GB. The problem again is that you'd need to raid two of the I-Ram devices together to get that much storage, and we don't even know if it would result in a tangible benefit.

    As others have mentioned, for all fast action games, it isn't the load times that Anand should be focusing on... its the in-game stutters when something suddenly has to get loaded from disk. Those are killer, and even if the initial game load times only decrease by 5%, if the stutters are eliminated, this might just be worth the cash, more than a new $600 video card certainly.
  • JarredWalton - Thursday, July 28, 2005 - link

    My point wasn't that WoW doesn't ever exceed 1GB, but that it doesn't exceed 2GB of RAM use. Actually, we should have probably mentioned that point as well: no single application under 32-bit Windows (not counting PAE/NUMA setups) can use more than 2GB of RAM. The 32-bit memory space is partitioned into 2GB for applications and 2GB for the OS, if I have my information right. Basically, you need to try out WoW with a 2GB setup before you can say that i-RAM would or wouldn't be able to help.

    Going back to the earlier statements, though, i-RAM is still nowhere near as fast as system RAM. The delay of PC3200 is around 140ns worst case, and bandwidth is still 3.2 GBps or 6.4 GBps dual-channel. i-RAM seems to be somewhere in the microseconds range for access times, and it's limited to 150 MBps bandwidth. If you can add RAM to your PC, that would be the first step to improving performance.
  • phonon - Wednesday, July 27, 2005 - link

    If you have Windows XP Pro, you should be able to make a volume that includes the I-RAM and a regular disk. Then you can make a hard links on the I-RAM that point to the additional 600 Megabytes or so on the regular disk that won't fit on the I-RAM. I've never done anything like this myself, but I think it should work. Any comments? Reply
  • johnsonx - Tuesday, July 26, 2005 - link

    someone's probably said all this, but i don't feel like reading all 80-odd comments:

    First, this strikes me more as a proof-of-concept effort. Sure, they'll sell you the engineering samples, for $150. Rev 2 will be the real product.

    Second, I did see several people suggest that interfacing the board to the SATA interface rather than directly to the PCI bus makes it slower. Why? Standard 32-bit 33Mhz PCI only has 133MB/s of bandwidth, and that's often shared by other devices as well. SATA has 150MB/s of bandwidth, and in most cases is connected to the system by at least a 66Mhz PCI link, or more often some other high-speed chipset link.

    Interfacing to SATA also means that Gigabyte doesn't have to write drivers for 32- and 64-bit flavors of Windows and various Linux distributions, MAC, and more obscure but definitely presents OSes like BSD, NetWare and Solaris (/me wonders about putting the boot partition and SYS volume of a NetWare server on an iRam... probably no real benefit, but you never know).

    Third, I might imagine that Rev 2 will support SATA II with 300MB/s transfer speeds, ECC, and perhaps 8 DDR slots.
  • rbabiak - Tuesday, July 26, 2005 - link

    Would have been nice to see some info on what it performed like as the temp folder for windows. all that internet web browser cache and other stuff that windows sticks off in the temp while it does stuff.

    this is data that you don't usally mind if it just disapears everyone in a while :)
  • UrQuan3 - Tuesday, July 26, 2005 - link

    I remember five or six years ago there were products that would plug into a PCI slot and use PC133 RAM to do this same job. They would show up as a harddrive controller and windows would use default drivers unless you needed something different. This was when programs didn't expect you to have enough RAM to keep a scratch file in RAM, so they'd write out files after every action. A PCI card with a gig of RAM for accepting these scratch files made a huge difference. There's just less need now.

    Then there's the other problem. SATA may be 150MB/s, but the PCI bus it's attached to is only 133MB/s. This certainly explains why everything runs at DDR200. If they'd made a PCI-X card there might be a bigger improvement. The bright side is that they used an FPGA. If next week they decide to implement SATA2, they can issue an update and everyone can upgrade their cards. Companies like Cisco do this several times a year in telecom products.
  • EODetroit - Tuesday, July 26, 2005 - link


    You can buy these still. Check out this ebay auction: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&...">http://cgi.ebay.com/ws/eBayISAPI.dll?Vi...egory=16...

    I'd hope and pray this thing is a lot faster than the iRam for all the extra cost. But the fact that it sits in a PCI card slot (I'm talking about the QikDrive linked above, not the iRam) makes me question that.

Log in

Don't have an account? Sign up now