In the last episode of , Paul
said:

The application is just stupidly designed, but hey, that's just
my opinion. Unless a machine has dropped to a "single-user"
configuration, where you're absolutely sure about resource
usage and what is safe, you shouldn't be doing that. It's
not like the memory is used in an intelligent fashion.
It's abusive, since the OS has a file system cache, which works
perfectly well, and is transparent to other RAM requests (it
backs off if there is any memory pressure at all). You could
use the properties of the file system cache, get to use
virtually all of the system memory for file caching, and
still offer memory instantly to any other application running
at the time that needs it. That preserves the responsiveness
of the machine, under any circumstances. Why they insist on
privately managing all of that "scratchpad" of memory, is
beyond me. One user reported it used 15GB of 16GB or so,
to give some idea how limitless it is. I couldn't test
that high on my laptop, because I have less memory than that.

Requesting a bunch of otherwise-unused RAM is perfectly safe and
harmless with a properly configured pagefile since the pagefile will
back the RAM allocation requests and RAM will only be assigned if
needed.

--
The nice thing about standards, there is enough for everyone to have their own.