I know this has been a topic of interest, but I still can't figure out what is happening. Take a look at the .jpg attached, and note that MEM USAGE and VM (Virtual Memory SIZE) show almost identical amounts, and they are in continuous flux. What is interesting is that the amount of DISK WRITE I/O stays the same throughout the flight, and is pretty low. Now, my VM size set in Advanced Performance settings in Windows is at 3,000mb, or 3x my installed RAM. So this seems to say the VM Size is being dynamically set to essentially match the amount of physical ram used by FS9, but that it really IS NOT using any VM to swap to. Why, because there is no DISK WRITE I/O happening for FS9 to speak of (value stays the same at about 38,635). Correct me if I misunderstand, but in order to actually USE VM, Windows has to WRITE to disk (as well as read from the pagefile). If this is true, there is surely no need to do anything special with setting Virtual Memory for FS9 when you have decent sized RAM, as it does not page to it anyway. Help if you have insight . . .Noel

Don't know why but this is just the way Windows seems to work. It's not just FS - VM usage is always the same as the total of RAM allocated, always has been. Anyone knows why? :)

Yes, paging file use also includes `anticipated` use of the VM, not the ACTUAL VM in use. It is this that is measured in Task Manager, not just the actual in-use portion.That's one reason why all the snake oil `fixes` for Windows XP Paging file are open to a degree of sniggering. When the designer of th paging file system advises the average user to leave windows to decide the VM size, you really have to listen. http://www.theeldergeek.com/paging_file.htmhttp://support.microsoft.com/kb/308417/Allcott

The main thing I've seen with paging files is that Windows managed paging files become fragmented very quickly on a Flight Simulator 2004 computer.Yes Microsoft recommends letting Windows manage the paging file for an average user.My company has one technical lead, one sales manager and three technical specialist - all Microsoft employees - assigned full time to our account / staff.The recommendation they received and passed on to us was to set the paging file as 2 to 4 times physical ram and set it as a set size right after the OS was installed. To ensure it was one contigious size.It seems that people who use Word, Excel and PowerPoint daily, often all at once - do not fit the definition of "Average User".One of the recommendations to improve performance in FS2004 - and most other games - is to rebuild the paging filehttp://support.microsoft.com/kb/815069/#XS...122120121120120This has the practical effect of resetting the paging file to a contigious space and eliminating the fragmentation - for a few FS sessions - then you can do it again.

Info I received at work (PC Engineer) was to set size as 3X RAM ant not let windows take over control which sounds about the same as what you said Reggie.Andrew Brownhttp://www.gordiusfs.pwp.blueyonder.co.uk/

Instead of using the task manager, why not try the performance monitor (which also allows logging)?scott s..http://forums.avsim.net/user_files/127118.jpgShould add that the "I/O read/write" is process I/O, and AFAIK doesn't have anything to do with page faults/swapping.