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

    • The problem isn't with Epic, it's with the platform holders like Steam and Nintendo, they should be a lot more strict in their review process.
    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
    • "it opens up new doors for people who prefer using Edge, but cannot be bothered to configure a Microsoft account" You already have a Microsoft account if you are using Windows 11, because you can't set it up without one.
  • 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
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      84
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!