{ Begin by giving some indication of load on the system during the day. The best way to do this is to look at the average amount of idol time on the system. This is just a general statement, it doesn't tell you if there was a period during the day where usage was very heavy. } IF AVE[Idle Time] >= 85 THEN "SYSTEM LOAD VERY HEAVY" IF AVE[Idle Time] >= 60 & AVE[Idle Time] < 85 THEN "SYSTEM LOAD HEAVY" IF AVE[Idle Time] >= 35 & AVE[Idle Time] < 60 THEN "SYSTEM LOAD NORMAL" IF AVE[Idle Time] < 35 THEN "SYSTEM LOAD LIGHT" {----------------------------------------------------------------------------} { Part 1 - Look at process states over the day } IF AVE[Mutex & Misc Resource Wait] > 0.1 | MAX[Mutex & Misc Resource Wait] > 1 THEN "EXCESSIVE NUMBER OF PROCESSES IN MWAIT STATES" { Things should never get to be COMO. The menu system should leave half the user processes in HIB state, these are the first target for outswapping. Going beyond hibernating processes, the system should then attack LEF people since there are a substantial number of users who log in and don't do anything. } IF MAX[Compute (Outswapped)] > 0 THEN "SOME PROCESSES WENT COMO." IF AVE[COMPUTE] > 1 THEN "SUBSTANTIAL NUMBER OF PROCESSES WAITING FOR CPU" {----------------------------------------------------------------------------} { Part 2 - Look at system memory utilization } IF AVE[System Fault Rate] > 0.3 THEN "SYSTEM FAULTING EXCESSIVE" IF MAX[System Fault Rate] > 5 THEN "PEAK SYSTEM FAULTING EXCESSIVE" { inswap rate of 0.1 on vax 750 (source: Digital Review 2/6/89 pg. 31)} IF AVE[Inswap Rate] > 0.1 THEN "INSWAP RATE EXCESSIVE" {----------------------------------------------------------------------------} { Part 3 - Look at the disk system } IF AVE[$DUA0: V751_SYS] > 20 THEN "AVERAGE I/O ON DUA0 EXCESSIVE" IF AVE[$DUA1: PSYCHO] > 20 THEN "AVERAGE I/O ON DUA1 EXCESSIVE" IF MAX[$DUA0: V751_SYS] > 35 THEN "PEAK I/O ON DUA0 EXCESSIVE" IF MAX[$DUA1: PSYCHO] > 35 THEN "PEAK I/O ON DUA1 EXCESSIVE"