How does AppManager track Windows virtual memory and the Windows paging files separately? (NETIQKB43692)

How does AppManager track Windows virtual memory and the Windows paging files separately?

AppManager uses various Perfmon counters to track virtual memory separate from page files for to several reasons:

• Virtual memory entails both physical memory and pagefile in combination.
• You can more than one page file.
• Windows documentation gives details of virtual memory with the following information: 'Virtual memory provides a logical view of memory that might not correspond to physical layout.'

Thus, Windows virtual memory is not necessarily made of a paging file. The pagefile can be used when virtual memory is exhausted and a request for more is needed.

AppManager uses the windows API to collect virtual memory\paging information and the details of what Windows is providing.

AppManager Online Help details the following information for the NT_MemUtil KS: Use this Knowledge Script to monitor physical memory, virtual memory, and the paging files. If any usage level exceeds the threshold you set, an event is raised.

Windows Online Help reports the following definition: 'Managing Computer Memory: When your computer is running low on RAM and more is needed immediately to complete your current task, Windows 2000 uses hard drive space to simulate system RAM. In Windows 2000, this is known as Virtual Memory, and often called the page file.'

Formerly known as NETIQKB43692