added a comment - - edited
The fix for 2.1.0 to this is to calculate the current page file extent using commit limit minus physical memory. This multiplied by usage fraction gives accurate estimate of actual page file size (and this is different than what appears under "Page File" of task manager, which is maximum potential usage).
However, for next minor release, we must replace the Swap Percentage Use indicator with either the ratio of Page File Size to Physical RAM, or just total page file size.
This is because page file size can be dynamic (and is so by default on Windows) and vary widely in size on identical machines. On Windows, where past maximum memory requirement largely determines the maximum page size. So 10% page file usage on a machine with a big page file may represent a bad memory situation, while it may be perfectly normal elsewhere.