Windows 10: How to force the memory uses of process/application from RAM to Page File and vice versa

As the title, how to force the memory use of Applications/Processes from memory to page file and vice versa on windows 10 and other windows?Please note that it does not relate to how to set the virtual memory Page file of Windows. This command aims to transfer memory from RAM to Page File and vice versa.However, I have no idea or keyword to search for it. Do you have any suggestions on which command can do that?Thanks!

:)

 

New laptop with 6GB of RAM is only using 3GB

????? unless you know a diffferent RamMap

 

Page file size?

A while ago I was reading somewhere that some applications crash without a pagefile, don't know about games though.

 

Out of memory on Nokia E60 - Use RAM?

The underlying operating system (OS), Symbian, does not yet have support for features known as paging and swapping.

Paging is a mechanism where lack of physical RAM can be compensated by copying chunks of RAM to a storage disk (a paging file) temporarily in order to free up RAM for some app that needs more momentarily (when the application/process whose memory pages were
pre-empted from RAM needs them again, they are read back from the paging file).

Swapping is a mechanism where an entire, idle process (application) is temporarily removed from RAM (all "pages" copied to a swap file, and then copied back when it needs to do something).

On a mobile device both of these pose a bit of a problem (not unsolvable, but which the designers of Symbian have decided not to implement/solve yet).

One of the problems is that an OS with paging/swapping support is a bit more complex and added complexity means more code and more cost (in development/test, storage space, price, etc.)

Another problem is that paging/swapping do not result in major issues with magnetic hard drives with no inherent limit as to how many times locations on the drive can be read or written to.

However, tbe big issues related to this with the so called Flash memory chips used in most mobiles is that Flash memory chips have actually a limit to how many read/write (especially write) cycles it survives, before the memory chip becomes unusable.

OS paging will result in a very significant increase in required memory write operations, which will mean that the Flash memory chips die much faster (or have to be replaced with much more expensive memory chips, possibly using entirely different technology).

It is possible, that even if the operating system has no paging/swapping support like this, individual applications could devise their own mechanism for it. It would lead to less of an issue or risk to Flahs memory than with the whole OS and all apps doing
paging, but it would make the application more complex and not really something any application should worry about individually (and hasn't, by whomever developed the browser app).