Now, We're Talking
I'll caution that
more RAM consumes more power and creates more heat. Laptop batteries and fans need to handle this. Desktops would probably already handle the cooling - but the run time while on battery backup during a power outage will be a bit shorter with more RAM.
Now, while we're at it (since you've now grabbed my attention fully lol), here's a discussion on the give-and-takes of RAM power consumption. Of course more NANDs will consume more power, but with less RAM, you're clearly going to have less cache...thus, more disk usage...and more power usage...
https://superuser.com/questions/40113/does-installing-larger-ram-means-consuming-more-energy
(Such an unexpected, yet intriguing reproach. I appreciate it...ensures that I'm not holding on to false beliefs as well)
If the user is not hitting the page file at 8GB, then what is gained by taking that to 16GB?
I have 8GB in this laptop and 16GB in my desktop. Neither hit the page file much - most of the time. Not even when starting a VM. However, if I load 6 VMs, then I'll need the page file. Or if I'm testing things with lots of browser tabs, then I'll need the page file.
It really depends on what a user is going to be doing most of the time. Just adding RAM might do more harm than good. Adding an SSD will vastly improve initial load times and boot/reboot times - but again, you don't reboot 80% of the time.
We are surely in agreement. I've actually starred this discussion as you caught me in the middle of a house move. lol And although I'm still moving in, I am cleaning out my email and noticed that I hadn't at least responded to your last response.
Although I agree that it matters what the User is doing with the machine to justify certain RAM configurations, I believe that everyone benefits from employing an SSD (where this discussion began, I believe). As we agree on that, there's nothing left but a Circle-Jerk.
A while ago (three years now), I became extremely annoyed in the "common approaches" of Virtual Memory implementation without any true logic behind it. The 2x or 1.5x approaches seemed reasonable, but if this was that straight forward, then why would Microsoft leave such room for manipulation...and why the vast differences in agreement (up to and including Techs and Enthusiasts who totally discarded using a pagefile at all.
You must keep in mind that the Pagefile, on top of all of this is NOT "additional RAM" nor a "cache file." It's most closely a "Swap File" but behaves in a significantly different way. Although now I pretty much leave it to Windows to decide what it needs (aka System Managed) while employing a pseudo RAID-0 of it across two SSDs (not my C in a RAID-0, I have two SSDs in my computer that do different jobs, and I have it System Managed across those two -- on my Server, anyway), I see absolutely nothing wrong with reserving 3x size for your pagefile if you have the additional space. Unlike RAM, it isn't really about using it up, it's about keeping Windows comfortable enough to put as many things in memory as possible.
Seems counter-intuitive, doesn't it?
This article by Mark Russinovich cleared up a lot for me back then. Maybe it'll give you a bit of insight as well...
https://blogs.technet.microsoft.com...pushing-the-limits-of-windows-virtual-memory/
PS: As an aside, I don't know what could ever encourage a User (Tech or otherwise) to run six VMs on one machine, but surely, unless you're running Android Emulations or something of this ilk, there must be a more efficient way to do whatever it is that you're doing. I have a gateway VM on my six-core with four hardware, server GB connections (soon-to-be hosting local DNS, web caching, and maybe DHCP), and I can't seem to think of anything more I would have to virtualize at Home. #justcuriousreally