Recommended Posts

Yes, it appears that Windows still follows the RAM x 1.5 formula for virtual memory that has existed since Windows 3.1! You'd think they would have revised that a little in the last decade or so. A similar crazy thing happens with the Recycle Bin as well, it still defaults to 10% of the hard drive (or of each hard drive if you have more than one), as it has since Windows 95 was released. The first thing I do when installing Windows is drop it down to around 1 or 2%. Even then I sometimes feel that it is wasteful.

I'm sure these crazy formulas probably have something to do with backwards compatibility, but I can't for the life of me understand what that might be. Maybe that is the reason that we still have the same font dialog box in Vista as in Windows 3.1 as well.

I doubt you have 12.2GB of virtual memory... You probably have 12.2GB total (physical plus virtual). Doesn't really matter, nothing goes there unless needed.

Brandon, I'm quite surprised that you would doubt that he was telling the truth about the virtual memory size, since you work for Microsoft. I'd think you would be well aware of the defaults that Windows ships with. 12GB of virtual memory would be the default setting for a system with 8GB of RAM (8 x 1.5 = 12).

I agree Conan, i've disabled virtual memory but it seems as though the sims 2 doesn't like that much, so i enabled it and up until today i followed the 1.5x rule, but i find it ridiculous to have 12gb of virtual memory.....so i dropped it. hopefully all is well.

I wonder if i should turn on readyboost too! lol

Brandon, I'm quite surprised that you would doubt that he was telling the truth about the virtual memory size, since you work for Microsoft. I'd think you would be well aware of the defaults that Windows ships with. 12GB of virtual memory would be the default setting for a system with 8GB of RAM (8 x 1.5 = 12).

I thought perhaps he was going by the "Page File" readout in Task Manager, which is actually physical RAM + virtual. On my machine it is 4GB + 4GB, so I don't know where the 1.5x thing comes from.

On my machine it is 4GB + 4GB, so I don't know where the 1.5x thing comes from.

Then you must have changed it from the default setting. Windows has used the RAM x 1.5 formula for virtual memory since it first had virtual memory. I remember it using up 1/4 of the 50MB hard drive in my first Windows machine (running 3.1) after I upgraded the machine to 8MB of RAM (huge at the time).

You cannot disable the page file without experiencing errors.

This might sound strange, but some things are FORCED into the paging file (Some kernel libraries are prime examples) even though they are cached back to normal ram, often they can be kept in page file just for refernce.

Blame windows, but having a "small" page file is the best way to go, i've often stuck with a 384-512mb one myself, right from the 1gb ram days. ;)

if you have that ammount of real memory then a pagefile size of 256mb or less will be best but dont turn it off,the more memory you got the less pagefile you need but it all depends on what you do with ur pc.

If I had 8 gig of ram I would sack the page file off completely to be honest. 8 gig should be more than plenty for most day to day stuff. If you are doing something seriously memory intensive I would consider buying more ram rather than paging (and increasing disk I/O) as the chances are the machine is critical and the cost for the extra ram would far outweigh the performance hit you get when using the page file. Why utilise your hard disk as slow memory when you can use fast RAM?

If I had 8 gig of ram I would sack the page file off completely to be honest. 8 gig should be more than plenty for most day to day stuff. If you are doing something seriously memory intensive I would consider buying more ram rather than paging (and increasing disk I/O) as the chances are the machine is critical and the cost for the extra ram would far outweigh the performance hit you get when using the page file. Why utilise your hard disk as slow memory when you can use fast RAM?

That shows a lot of ignorance of OS design. Regardless of how much RAM you have, you shouldn't completely disable your pagefile. Make it small, sure, if you care about the disk space it's taking up. But don't turn it off.

You CAN turn it off, it's just not a good idea.

Then you must have changed it from the default setting. Windows has used the RAM x 1.5 formula for virtual memory since it first had virtual memory. I remember it using up 1/4 of the 50MB hard drive in my first Windows machine (running 3.1) after I upgraded the machine to 8MB of RAM (huge at the time).

Nope, it's using purely default settings - set to "Let windows manage my pagefile" or whatever. The size is actually variable, not fixed though.

I thought perhaps he was going by the "Page File" readout in Task Manager, which is actually physical RAM + virtual. On my machine it is 4GB + 4GB, so I don't know where the 1.5x thing comes from.

You've most likely set your Pagefile to a custom or constant size Brandon.

Windows default pagefile formula since Win95 has been Physical Mem x 1.5 =pagefile.sys size.

Also soldier1st 8GB of RAM sounds about right for Crysis or any game that uses large or streaming textures.

Instead of having the videocard texture swapping to the HD you could have it done in the RAM and just shut off the pagefile.

Any amount of RAM, 1gig or 8gig - I would still allow the OS to allocate it and work with a pagefile. It's a feature that the OS expects, and so denying it would be derogatory to the OS.

How so? The pagefile exists as a file on the HD. Max transfer speeds on an HD are around 1% of RAM speeds at best.

By disabling the pagefile you're forcing that information to travel at around 100+ times the speed.

How would that be derogatory? (BTW I'm assuming you meant detrimental, not derogatory)

  • 6 years later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Couple years ago I got a brand new 4TB Samsung 990 Pro for $250 during Black Friday
    • Thanks
    • Can confirm, I've built stuff for others and no complaints using their products.
    • Yes I agree, it's annoying. You can now miss tabs unless you point low enough.
    • Sysinternals Suite 2026.17.06 by Razvan Serea The Sysinternals Suite is a comprehensive package of advanced Windows utilities created by Mark Russinovich, who launched the Sysinternals website in 1996 to share his system tools and technical resources. This suite combines a wide range of troubleshooting and diagnostic tools, including Process Explorer, Process Monitor, Sysmon, Autoruns, ProcDump, the PsTools collection, and many others. It provides everything IT professionals and developers need to manage, monitor, and troubleshoot Windows systems and applications. The Suite bundles all of the core troubleshooting utilities along with their help files. Non-troubleshooting extras—such as the BSOD Screen Saver or NotMyFault—are excluded. In addition to the well-known tools, it also includes AccessChk, Autologon, Ctrl2Cap, DiskView, Disk Usage (DU), LogonSessions, PageDefrag, PsLogList, PsPasswd, RegMon, RootkitRevealer, TCPView, VMMap, ZoomIt, and more. Sysinternals Suite 2026.17.06 changelog: Autoruns v14.3 - This update to Autoruns, a utility for monitoring startup items, adds bug fixes and improves the command-line application autorunsc. ZoomIt v12.1 - This update to ZoomIt, a screen magnification and annotation tool, adds image backgrounds, webcam background blur and microphone noise cancellation support. Coreinfo v4.01 - This update to Coreinfo, a tool that reports processor, socket, NUMA memory, and cache topology of a system, as well as processor features supported, adds support for new processor features. DebugView v5.02 - This update to DebugView, a tool for displaying both kernel-mode and Win32 debug output, adds Ctrl-Shift-A support for selecting all output, and agent skills support for the CLI utility. LiveKd v5.64 - This update to LiveKd, a utility that allows running the kernel debugger on a live system, fixes a debugging privileges issue. ProcDump 3.5.2 for Linux - This update to ProcDump for Linux, a tool for capturing process dumps, adds .NET counters and a custom core dumper. Process Monitor v4.04 - This update to Process Monitor, a utility for observing real-time file system, Registry, and process or thread activity, adds some bug fixes Sysmon v15.21 - This update to Sysmon, an advanced host security monitoring tool, adds some bug fixes. Download: Sysinternals Suite 2026.17.06 | 168.0 MB (Freeware) Download: Sysinternals Suite for ARM64 | 15.4 MB Link: Sysinternals Suite Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      542
    2. 2
      +Edouard
      169
    3. 3
      PsYcHoKiLLa
      85
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!