How do i fix windows garbage memory management
ive had to limit the swap file because im running out of disk
LOL
It is important to understand it is the user's responsibility to ensure the operating system has enough free disk space to operate in. So I find it amusing, sad and ironic when Windows is accused of "garbage memory management" when it is the user who has failed to properly manage the computer resources.
Contrary to what some folks think, and worse, what many want everyone else to believe, the developers at Microsoft are not stupid. I can't say the same for the marketing weenies or some of the executive decisions - but that's for a different discussion. But when it comes to Windows development, Microsoft has had decades of time and multiple exabytes of empirical data to analyze and use. And they have top experts with PhDs and other advanced degrees in the computer sciences, with super computers at their disposal to crunch that data, run millions and millions of different scenarios, and evaluate results the ensure Windows most effectively and efficiently utilizes
and manages system resources - AS LONG AS the user
doesn't dink with the default settings. So it amazes me how some, typically with little to no formal training or education in virtual memory management, think they are smarter than MS at virtual memory management.
Or they think their system is so unique, it requires manual management. That is total nonsense. 99% (probably more than that) of the computers used today fall into the "normal" configuration range and therefore, Windows knows how to manage virtual memory just fine.
You solution is obvious. If you are running out of disk space, so you need more disk space. You need to uninstall programs you no longer use, move user files off to another drive, and/or buy more disk space. Then restore the defaults for the page file to
let Windows manage it!
then crash for no reason
and before you say upgrade your ram
their was 10 GIGS of REAL ram free at the time so it did NOT need to use swap
LOL Crashes
always, as in EVERY SINGE TIME, happen for a reason. Just because we don't see, don't know, or don't understand the reason, that does NOT mean Windows is to blame.
Sorry, but this illustrates my point. And
in your defense, it is a common misconception so you are not alone. That totally incorrect information about having lots of RAM negates the need for a properly sized PF is sadly based on myths and other misinformation spewed about by those who think they know more than the experts.
It is simply false to suggest a PF is not needed if you have lots of RAM. Windows will always take advantage of it, and many programs require one, regardless how much physical RAM is installed. And I find the most common justification given to disable it, or reduce and/or restrict its size even more ironic. It is usually something along the lines of, "I disabled it and it didn't break Windows so it must be fine".
With today's modern Windows, and Windows ability to dynamically adjust the PF size as needed, there really is only one change to the defaults for virtual memory management that makes sense - in some cases. And that is when you have more than one physical drive installed, it is sometimes beneficial to create another page file on a secondary drive. So for example, if you have a small (or slow) boot drive, and a big (or faster) secondary drive, it may make sense to enable a PF on the secondary drive. And the good news is, Windows is again smart enough to use the fastest drive when possible. But note for crash dumps, the boot drive is always used. So the recommended setup is to enable "Windows managed" PFs on both (or even all) drives - then LEAVE THE SETTINGS ALONE.
clearly, your program needs more swap file so... free up space and give it more swap file.
Exactly. Well, ROH1T is right - these days, the swap file and PF, while both caches, are different. But Mussels' point is spot on - you need more disk space.
