Available Megabytes of Memory Monitor

Operational States

Name State Description
Available Memory OK Success Available Memory OK
Available Memory Critical Error Available Memory Critical

Overridable Parameters

Parameter Name Default Value Description Override
Interval seconds 120 How frequently (in seconds) the value should be sampled.
Timeout Seconds 100  
Available Memory Threshold (MBytes) 100  
Number of Samples 3  

Alert Details

Monitor State Message Priority Severity Auto Resolution
Available Memory Critical (Error) Available Megabytes of Memory is too low Medium Critical Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

The Available MBytes (Memory\% Available MBytes) for the system has exceeded the threshold. Overall system performance may significantly diminish which will result in poor operating system and application performance.

Available MBytes is the amount of physical memory that is available for use by applications and processes.

Causes

The amount of available physical memory can become low under the following circumstances:

  • Too many applications are running simultaneously on the computer.

  • An application may be leaking memory over time.

Resolutions

To view recent history for the Memory\% Available MBytes counter you can use the following view:

Start Memory Available MBytes Performance View

To address a low physical memory condition an administrator may chose one or more of the following options:

  • Close or stop one or more applications, services, processes.

  • Add additional Physical Memory to the computer.

  • Move applications to one or more additional servers.

If the system has been adequately provisioned with physical memory and application load but it continually exceeds the available physical memory threshold over time, it is possible that an application is leaking memory. To identify an application that is leaking memory, do the following:

Open System Monitor and monitor the following system wide performance counters over time:

  • Paging File\% Usage

  • Paging File\%

  • Memory\Pool Nonpaged Bytes

  • Memory\Pool Paged Bytes

If any one of these counters continually increase over time, it is possible that an application may be leaking memory.

If the system appears to be leaking memory, the specific application can be identified by monitoring the following counters for each running process:

  • Process\Page File Bytes

  • Process\Pool Nonpaged Bytes

  • Process\Pool Paged Bytes

  • Process\Private Bytes

  • Process\Thread Count

If you observe a consistent and significant increase in any of these counters, it may be necessary to contact the application vendor for support.

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