Memory Pages Per Second Monitor

  • ID:  Microsoft.Windows.Server.2008.OperatingSystem.MemoryPagesPerSecond
  • Description:  Monitor the performance counter Memory\MemoryPagesPerSecond
  • Target:  Windows Server 2008 Operating System
  • Enabled:  Yes

Operational States

Name State Description
Pages Per Second High Warning Memory Memory Pages Per Second High.
Pages Per Second OK Success Memory Pages Per Second OK.

Overridable Parameters

Parameter Name Default Value Description Override
Frequency 300  
Threshold 5000  

Alert Details

Monitor State Message Priority Severity Auto Resolution
Pages Per Second High (Warning) Memory Pages Per Second is too High. Medium Warning Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

The rate at which the system is paging memory to and/or from disk is too high. This monitoring is based on the “Memory\Pages/sec” counter, which is a primary indicator of the kinds of faults that cause system-wide delays. Overall system performance may significantly diminish.

Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults.

Causes

One or more applications are using memory heavily, and the system is having to page data to and from disk to meet the demand.

Resolutions

To identify which processes are driving up the overall memory utilization on the system, and the paging rates use the following counters from the “Process” object in performance monitor:

  • Page Faults/sec: Page Faults/sec is the rate at which page faults by the threads executing in this process are occurring. A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This may not cause the page to be fetched from disk if it is on the standby list and hence already in main memory, or if it is in use by another process with whom the page is shared.

  • Pool Nonpaged Bytes: Pool Nonpaged Bytes is the size, in bytes, of the nonpaged pool, an area of system memory (physical memory used by the operating system) for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated. Memory\\Pool Nonpaged Bytes is calculated differently than Process\\Pool Nonpaged Bytes, so it might not equal Process\\Pool Nonpaged Bytes\\_Total. This counter displays the last observed value only; it is not an average.

  • Pool Paged Bytes: Pool Paged Bytes is the size, in bytes, of the paged pool, an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used. Memory\\Pool Paged Bytes is calculated differently than Process\\Pool Paged Bytes, so it might not equal Process\\Pool Paged Bytes\\_Total. This counter displays the last observed value only; it is not an average.

Based on the findings from further investigation resolutions will vary and could include one of the following:

  • Apply updates to the operating system or the applications to ensure that any known memory issues are fixed.

  • Scale back the number of applications running on the system, or the amount of load that the system is undertaking.

  • Add more RAM to the system.

External References
This monitor does not contain any external references.

See Also for Windows Server Operating System Management Pack


Downloads for Windows Server Operating System Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED