I have 32 GB ram @ 3600 mhz (2x16) on Samsung Evo Plus 970 2TB (SSD). How much should I set the virtual memory for?
I am very confusing about it.
I am very confusing about it.
There is a difference between "not having to do this anymore" and "doing it when you have no choices".
There are far more threads about people NOT using the "Let Windows manage it" option than the opposite. I can't remember the last time I saw someone say "That fixed it by setting a page file size and location manually instead of using auto".
Installing drivers manually is again if you have no choices. Most drivers comes in an installation package now and only a few will make you extract an inf file and make you use device manager. Like I said this isn't 1995 anymore. Back in the days you had to do this for every device with a ! in device manager and there were a lot of them. Now you install the Chipset drivers and the GPU...
You can do this or set it for a fixed value of 32GB minimum and 32GB maximum. This was a trick we used back in the old days to give the system a permanent fixed size swap file.Are you talking about Windows Virtual memory / pagefile? You leave it at auto managed by the system.
You can do this or set it for a fixed value of 32GB minimum and 32GB maximum. This was a trick we used back in the old days to give the system a permanent fixed size swap file.
That is incorrect. I was having some issues with a piece of software and I was able to fix it by setting up a permanent swap file. Now, granted this software is designed to 'snapshot' the system and make it the same each boot like a toaster, but the swap file constantly changing was messing it up after a memory upgrade.In the old days. You said it. Nowadays you do not need to do this anymore. We have enough RAM to let Windows take care of it without having an issue. Back in the days you had no choice in some situations. In 2021 you do not touch this option unless you want to change the pagefile location to put it on another drive.
This is the equivalent of installing your drivers manually through device manager only. No need to do it like that anymore.
Yep until an update comes along and breaks it, lol.Haha, right..computing has come a long way hasn't it. System managed...Set, Restart and compute in peace.
Like adjusting the swap file or installing drivers--LOL!!Hopefully not, but then again we'll find other way for it to work....
Like adjusting the swap file or installing drivers--LOL!!
It's sad that a lot of times the system gets so borked that the only solution is a complete reinstall--it's a waste. 🙁
Yep, qc in programming is next to nothing these days. And computers and devices are strategically planned for obsolescence to make companies and people in power money...easy to rig the deck when you make the cards...😉Well keeps having fun installing OS, finding new ways to circumvent error made by poor programing...merely computing along...
That is incorrect. I was having some issues with a piece of software and I was able to fix it by setting up a permanent swap file. Now, granted this software is designed to 'snapshot' the system and make it the same each boot like a toaster, but the swap file constantly changing was messing it up after a memory upgrade.
It still helps to have a contiguous permanent swap file. Because drives are faster (especially with ssds) you may not notice the difference, but that doesn't mean it's there.
And you still do have to install drivers manually--lots of threads on here where people have had to do this for video and network cards, even motherboards.
Bottom line is to know how things work and adjust accordingly. If you really want to tweak a system, understand how the system works in theory and then act accordingly. The theory on swap files hasn't changed, so all the old tweaks still work.
The problem is that windows management of a swap file was terrible from day one--and like the word wrap bug in notepad that stuck around forever, they never really changed the swap file either. I didn't think it was an issue until I started messing with it again. It's why there's a permanent swap file in any of the IOT or embedded versions of windows even though those machines typically have an ssd as well.There is a difference between "not having to do this anymore" and "doing it when you have no choices".
There are far more threads about people NOT using the "Let Windows manage it" option than the opposite. I can't remember the last time I saw someone say "That fixed it by setting a page file size and location manually instead of using auto".
Installing drivers manually is again if you have no choices. Most drivers comes in an installation package now and only a few will make you extract an inf file and make you use device manager. Like I said this isn't 1995 anymore. Back in the days you had to do this for every device with a ! in device manager and there were a lot of them. Now you install the Chipset drivers and the GPU drivers and everything works perfectly.
Nowadays the amount of people that needs to do any of this is almost non existent. We see a thread like that once in a month.
For 99.99% of the people this is irrelevant.
From https://docs.microsoft.com/en-us/archive/blogs/e7/support-and-qa-for-solid-state-drivesWhat about the goal of minimizing writes to an SSD in order to lengthen it's useful lifespan?
Isn't that why some people advise us to move the pagefile off the C: drive (if it is an SSD) to an HDD?
But what if you don't have an HDD?
I guess in that case the advice would be to try turning paging off, and if that's too slow, then set the pagefile to a fixed size.
I've been using SSDs as my OS drive and kept the page file on the SSD for at least 7 years now. I've averaged around 2-3TBW per year, and given that most highly recommended SSDs still have a wear rating of at least ~100 TBW, I think I'm going to toss any SSD long before the flash wears out.Should the pagefile be placed on SSDs?
Yes. Most pagefile operations are small random reads or larger sequential writes, both of which are types of operations that SSDs handle well.
In looking at telemetry data from thousands of traces and focusing on pagefile reads and writes, we find that
In fact, given typical pagefile reference patterns and the favorable performance characteristics SSDs have on those patterns, there are few files better than the pagefile to place on an SSD.
- Pagefile.sys reads outnumber pagefile.sys writes by about 40 to 1,
- Pagefile.sys read sizes are typically quite small, with 67% less than or equal to 4 KB, and 88% less than 16 KB.
- Pagefile.sys writes are relatively large, with 62% greater than or equal to 128 KB and 45% being exactly 1 MB in size.
If you're worrying about wearing out an ssd because of virtual memory usage, you need more physical memory because you shouldn't be swapping that much (even though windows will swap everything to a swap file if you let it).What about the goal of minimizing writes to an SSD in order to lengthen it's useful lifespan?
My system is SSD only. Indeed, (almost) ALL my house systems are SSD only.What about the goal of minimizing writes to an SSD in order to lengthen it's useful lifespan?
Isn't that why some people advise us to move the pagefile off the C: drive (if it is an SSD) to an HDD?
But what if you don't have an HDD?
I guess in that case the advice would be to try turning paging off, and if that's too slow, then set the pagefile to a fixed size.
A little late to the party.......I suspect this may be a user specific thing.I have 32 GB ram @ 3600 mhz (2x16) on Samsung Evo Plus 970 2TB (SSD). How much should I set the virtual memory for?
I am very confusing about it.
win 10 should have just set it to 4gb. If you never use all of your ram, it will never use a page file.I have 32 GB ram @ 3600 mhz (2x16) on Samsung Evo Plus 970 2TB (SSD). How much should I set the virtual memory for?
I am very confusing about it.