Page Hits Alarm
This alarm is activated when the proportion of page requests that can be sourced from memory rather than disk drops below a threshold.
When this alarm is current you should:
- Look at the Paging chart in the Summary page of the Memory drilldown to see if a high level of paging has been occurring for an extended period. Spikes in requirements are expected.
-
Look at the Page Faults/sec column on the Processes page in the Processes drilldown.
This will tell you which applications are making the most page requests. If this is an ongoing problem, look at spreading the load between multiple systems.
- Look at increasing the physical memory of the system.
Related Topics
Summary Page
Processes Page
Page Outs Alarm
This alarm is activated when the number of pages being written to disk exceeds a threshold. Sustained high paging rates can adversely effect the performance of a system.
Only those pages that have been altered are written to disk. Pages that have not been changed are dropped.
When this alarm is current, you should:
-
Look at the Processes page on the Processes drilldown to see which process is causing the paging. Look at the Page Faults/sec column. This will help you determine the cause of paging.
A high level of page faults and page outs indicates memory thrashing. If this is the case, the system may require more memory.
- Look at the Paging chart on the Summary page of the Memory drilldown. This shows how long the high paging has been occurring. Short periods of high paging are acceptable, but if the paging rate is high for a sustained period, there may be a problem with the system.
- Consider adding more physical memory to the system.
- Stop unnecessary services and processes on the system.
Related Topics
Processes Page
Summary Page
Page Reads Alarm
This alarm is activated when the number of pages being read in exceeds a threshold. Sustained high paging rates can adversely effect the performance of a system.
When this alarm is current, you should:
- View the Processes page on the Processes drilldown to see which process is causing the paging. Look at the Faults/s column to determine the cause of paging.
- View the Page File Transfers chart on the Paging Activity page of the Memory drilldown. This shows how long the high paging in has been occurring. Short periods of high paging are acceptable, but if the paging rate is high for a sustained period, there may be a problem with the system.
- Consider adding more physical memory to the system.
- Stop unnecessary services and processes on the system.
Related Topics
Processes Page
Summary Page
Page Writes Alarm
This alarm is activated when the number of pages being written to disk exceeds a threshold. Sustained high paging rates can adversely effect the performance of a system.
Only those pages that have been altered are written to disk. Pages that have not been changed are dropped.
When this alarm is current, you should:
- Look at the Processes page on the Processes drilldown to see which process is causing the paging. Look at the Page Faults/Second column to determine the cause of paging. A high level of page faults and page outs indicates memory thrashing. If this is the case, the system may require more memory.
- View the Paging chart on the Summary page of the Memory drilldown. This shows how long the high paging has been occurring. Short periods of high paging are acceptable, but if the paging rate is high for a sustained period, there may be a problem with the system.
- Consider adding more physical memory to the system.
- Stop unnecessary services and processes on the system.
Related Topics
Processes Page
Summary Page
