VM Validator allows you to analyse a program's virtual memory performance in a graphical manner. This is much more useful than a binary dump of page addresses that can be found in various books on undocumented secrets about Windows NT® books. As the display changes you can identify areas that are repeatedly paged in and then paged out. When these areas have been identified you can make changes to your program's memory management to try to reduce the page swapping.
VM Validator has been created with the following criteria in mind.
1) VM Validator must have no adverse effect on the program's behaviour.
The program must behave in the same way when being inspected by VM Validator as when the program is running without being inspected by VM Validator.
2) VM Validator must be reliable and avoid causing the target program to crash.
3) VM Validator must be capable of having as little impact on the target programs performance as possible.
4) VM Validator's user interface must be independent of the target program.
VM Validator's user interface is independent of the target program.
•If the VM Validator user interface crashes, your target program will not crash.
•If the target program crashes the VM Validator user interface will not crash - you will still have data to work with.
•If the target program is stopped in the debugger, VM Validator's user interface will continue to work.
Where there are multiple ways of presenting the data, the user should be given a choice over how that display works. Not all users like the same choices, so providing some choice over the display is always better than forcing all users to use the same settings.