Previous Topic: Interpret the Analysis ReportsNext Topic: CPU Rule Analysis Report


Memory Rule Report

The following example shows a Memory Rule report:

Full Analysis NODE01 (VAXstation 3100) Page 1

PA Vx.x

Thursday 20-FEB-1997 00:00 to 23:59 CONCLUSION 1. While excessive page faulting was occurring, there were some users running images which seemed to want more memory than their WSEXTENTS allowed. If the WSEXTENTS for these users were larger, there may have been less page faulting. Increase the WSEXTENT for the following users. If batch queue settings for working set extents are causing the limitation, increase those. If detached processes are causing the problem, increase the working set extents specified in either the "RUN/PROCESS" commands, or the calls to the $CREPRC System Service or LIB$SPAWN Runtime Library Routine. As a last resort for detached processes, increase the PQL_DWSEXTENT SYSGEN parameter if it is responsible for establishing the working set extent value for the detached process. Total number of users needing an increase : 2 User name(s) ------------ SMITH CORREY CONDITIONS 1. SOFT_FAULT_RATE .GE. 100.00 * SOFT_FAULT_SCALING .OR. HARD_FAULT_RATE .GE. 10.00 * HARD_FAULT_SCALING 2. IMAGE_ACTIVATION_RATE .LT. 0.50 * IMG_ACT_RATE_SCALING 3. SYSGEN_MPW_HILIMIT + SYSGEN_FREEGOAL .LT. MEMORY_PAGES_NOT_ALLOC_TO_VMS * ( 0.04 + 0.05 ).OR. PAGES_ON_FREELIST .GE. SYSGEN_FREEGOAL .OR. HARD_FAULT_RATE .GE. 10.00 * HARD_FAULT_SCALING 4. SYSGEN_MPW_HILIMIT + SYSGEN_FREEGOAL .GE. MEMORY_PAGES_NOT_ALLOC_TO_VMS * 0.05 .OR. SOFT_FAULT_RATE .GE. 100.00 * SOFT_FAULT_SCALING 5. PROCESSES_NEED_MORE_EXTENT .EQ. 1.00 6. OCCURRENCES .GE. 1 EVIDENCE Working Set Time range Avg Image Faults Avg sz No User ------------ (batch jobs Image W.Set flts/ ----------- of Free of Name Quota Extent are flagged) Name Size cpusc Hrd Soft List Tims ----- ----- ------ ----------- ------ ---- ----- --- ---- ----- ---- 1 2 3 4 5 6 7 8 9 10 SMITH 200 200 11:34-13:34 LOGINOUT 163 288 1 288 12262 4 11:34-15:14 TEST31 195 268 0 268 12468 5 11:34-13:30 SET 179 363 2 363 12765 2 CORREY 2048 4000 (batch) 13:16-13:18 TEST33 4000 2046 0 2046 11162 2

The following statements are keyed to the columns in the previous Memory Rule report:

  1. User name associated with a process.
  2. Working set quota and working set extent.
  3. Time range for which selected image records for this process are summarized.
  4. The first 12 characters of the image name string associated with the user's process.
  5. Average working set size (in pages) for the user's process while running the specified image.
  6. Total number of page faults for the user's process while running the specified image, divided by the CPU seconds for the same period.
  7. Average system-wide hard page fault rate during the major sampling intervals when the user's process ran the specified image.
  8. Average system-wide soft page fault rate during the major sampling intervals when the user's process ran the specified image.
  9. Average size of the free page list (in pages) during the periods when the user's process ran the specified image.
  10. Number of times that a Performance Manager process or image record supports the evidence.

In the previous Memory Rule report example, the total number of page faults per CPU second are in the range of 268 to 363 for user Smith, and 2046 for user Correy. This high rate of page faulting probably contributed to the system-wide soft page fault rate (ranging from 106 to 791), which exceeded the threshold of 100. This occurred 13 times (4+5+2+2) because Smith's WSEXTENT was too low at the current value of 200 and Correy's WSEXTENT was too low at its value of 4000.