Virtual Memory Validator - Overview
VM Validator allows the virtual memory behaviour of an application to be
monitored. As virtual memory is consumed, memory is paged out from physical
memory to disk storage, and memory is paged in to physical memory from disk
storage. VM Validator allows you to examine which pages are physically present
in memory and thus gain a better understanding of your application's virtual
memory usage. Typically, the more paging behaviour, the worse the performance
(in speed terms) of the application. By analysing which parts of your application
cause the behaviour monitored by VM Validator you can determine which parts
of the application can benefit from different memory allocation algorithms
and different memory access algorithms.
You can view information on individual
features of VM Validator by taking one of the links at the left of this text,
or you can follow the link at the bottom of the page to move to the next feature.
You can use VM Validator in three ways:
- Inject VM Validator into an already running executable
- Specify an executable to start, and VM Validator will attach to that executable
- Specify an executable to watch, and VM Validator will wait for the executable to start, then VM Validator will attach to that executable. This feature is very useful for attaching to OLE servers that start when a document is opened inside a 3rd party application
VM Validator is provided free of charge, as a complement to the Memory Validator product. The initial version of VM Validator has been released to see what demand there is for a tool like this. At present the data gathering can be considerably improved, and there are no analysis tools.
VM Validator will be updated with speed improvements and analysis capabilities
later this year.
View the feature
list for Vitual Memory Validator.
