Virtual memory and page file
, although it is easy to misunderstand that the part that corresponds to virtual memory does not refer to the page file usage (%).
What the virtual memory of this old function points to is the amount of reserved memory area called commit in later OSes, and thilmera used to treat this number as a page file.
In the current thilmera, the page file shows the amount of memory occupied in the HDD by obtaining the file path specified in the physical page file, checking the file size, and calculating the percentage.
Therefore, the page file of thilmera is the usage amount (rate) of the page file in the physical HDD, and is completely different from virtual memory.
Also, if you are using a 64-bit OS and have more than 8GB of physical memory, the page file may not change from 0, but this is normal.
Windows XP and later versions are structured to avoid swapping out (extruding the HDD) as much as possible, so you should use apps that assume the use of swap files, or use them for several days or start a large number of apps. I think it will work if you do something like this.
However, this does not mean that the swap file is not used at all, so even in a test on an aircraft with 32 GB of memory, a page file of about 3 GB was used after 50 days of operation. Even if there is enough physical memory.
So, if you want to know the commit (reserved memory amount), display the commit charge.
If you want to know the physical usage of page file, please refer to page file display.