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

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!