 |
OpenVMS System Management Utilities Reference
Manual
The data items can also be displayed as percentages of all processes.
Note that the Current Process is always the process running MONITOR,
because MONITOR is running when each measurement is made.
For performance reasons, MONITOR does not synchronize the scanning of
process state data structures with operating system use of those
structures. It is therefore possible that MONITOR will display certain
anomalous state indications.
Example
|
$ MONITOR/INPUT/SUMMARY/NODISPLAY -
_$/BEGINNING=29-APR-2000:13:00 -
_$/ENDING=29-APR-2000:14:00 STATES/PERCENT/ALL
$ TYPE MONITOR.SUM
OpenVMS Monitor Utility
PROCESS STATES (%)
on node SAMPLE From: 29-APR-2000 13:00:00
SUMMARY To: 29-APR-2000 14:00:00
CUR% AVE% MIN% MAX%
Collided Page Wait 0.0 0.0 0.0 0.0
Mutex & Misc Resource Wait 0.0 0.0 0.0 0.0
Common Event Flag Wait 0.0 0.0 0.0 0.0
Page Fault Wait 4.3 1.4 0.0 4.3
Local Event Flag Wait 34.7 31.7 34.7 42.8
Local Evt Flg (Outswapped) 0.0 9.0 0.0 19.4
Hibernate 43.4 40.7 43.4 52.1
Hibernate (Outswapped) 0.0 4.3 0.0 15.4
Suspended 0.0 0.0 0.0 0.0
Suspended (Outswapped) 0.0 0.0 0.0 0.0
Free Page Wait 0.0 0.0 0.0 0.0
Compute 13.0 7.3 4.3 13.0
Compute (Outswapped) 0.0 0.8 0.0 3.2
Current Process 1.0 1.0 1.0 1.0
PLAYBACK SUMMARIZING
|
|
The commands in this example generate and display a PROCESS STATES
summary. Note that since use of the Return key is not permitted within
a single MONITOR command following the MONITOR> prompt, the MONITOR
command is entered at DCL level. The summary shows that, on the
average, 14.1 percent of processes were swapped out for the summarized
period. Note that the summary was requested for data covering only the
hour between 1 P.M. and 2 P.M., although the input file could have
contained data covering a longer period.
MONITOR SYSTEM
The MONITOR SYSTEM command initiates monitoring of the SYSTEM
statistics class, which shows several of the most important items from
other classes.
Format
MONITOR SYSTEM
Command Qualifiers
/qualifier[,...]
One or more qualifiers as described in the Command Qualifier
Descriptions section.
Classname Qualifiers
/ALL
Specifies that a table of all available statistics (current, average,
minimum, and maximum) is to be included in the display and summary
output. For summary output, this qualifier is the default for all
classes; otherwise, it is the default for all classes except CLUSTER,
MODES, PROCESSES, STATES, SYSTEM, and VECTOR.
/AVERAGE
Specifies that a bar graph of average statistics is to be included in
the display and summary outputs.
/CURRENT
Specifies that a bar graph of current statistics is to be included in
the display and summary outputs. The /CURRENT qualifier is the default
for the CLUSTER, MODES, STATES, SYSTEM, and VECTOR classes.
/MAXIMUM
Specifies that a bar graph of maximum statistics is to be included in
the display and summary outputs.
/MINIMUM
Specifies that a bar graph of minimum statistics is to be included in
the display and summary outputs.
Description
Because the SYSTEM class collects the most significant performance
statistics from other classes in a single display, it is particularly
useful to system managers and other users seeking a general overview of
system activity. The SYSTEM class includes the following data items:
Interrupt Stack (on VAX systems) or Interrupt State (on Alpha systems)
MP Synchronization
Kernel Mode
Executive Mode
Supervisor Mode
User Mode
Compatibility Mode (meaningful on VAX systems only)
Idle Time
Process Count
Page Fault Rate
Page Read I/O Rate
Free List Size
Modified List Size
Direct I/O Rate
Buffered I/O Rate
The following two display formats are provided, depending on the
classname qualifier specified:
- A tabular style format for the /ALL qualifier
- A bar graph style format for the /AVERAGE, /CURRENT, /MAXIMUM, and
/MINIMUM qualifiers
Examples of these formats are at the end of this section. Note that the
bar graph version of the SYSTEM class (shown in Example 2) contains the
following data, which differs from the tabular version:
- All of the CPU processor modes except Idle Time are summarized in
the CPU Busy segment.
- In the Page Fault segment, the page read I/O rate is indicated by a
vertical bar. The bar provides a visual estimate of the proportion of
the total page fault rate that caused read I/O operations (the hard
fault rate). The hard fault rate appears to the left of the bar.
- Four segments show the processes that are currently the top
consumers of CPU (since the last screen update), page faults, direct
I/Os, and buffered I/Os.
Beginning in OpenVMS Version 7.3, the following rate fields have
increased in the MONITOR SYSTEM bar graph screen display:
| Rate Name |
Old Rate |
New Rate |
|
Page Fault
|
100
|
500
|
|
Hard Page Fault (vertical line on Page Fault display)
|
100
|
500
|
|
Direct I/O
|
60
|
500
|
|
Free List Size
|
Shown in K blocks
|
Shown in K, M, or G blocks (whichever is appropriate)
|
|
Mod (modified) List Size
|
5 digits; K blocks
|
8 digits; K, M, or G blocks (whichever is appropriate)
|
|
Buffered I/O
|
150
|
500
|
Any process that MONITOR designates as a top user process must be
swapped in at the beginning and ending of the display interval or at
the beginning and ending of the entire period covered by a summary.
When the lower bar graph (top user) and the corresponding upper bar
graph (overall system measure) are tracking the same statistic for the
same interval (as in Example 2), it is reasonable to compare the two
graphs. This will be the case in the following situation:
- SYSTEM is the only class being monitored (no other class names have
been specified with the MONITOR command).
- The CURRENT statistic is specified.
- The /INTERVAL and /VIEWING_TIME values are equal.
Otherwise, exercise care in making such comparisons because the top
user statistic is always CURRENT, while the overall system measure
statistic may be CURRENT, AVERAGE, MAXIMUM, or MINIMUM.
Rates for top users are calculated based on the interval between two
successive screen displays, while overall system rates are based on the
collection interval. These two interval values can be different
whenever one or more classes are being monitored with the SYSTEM class,
or when /INTERVAL and /VIEWING_TIME values differ.
While other upper boundary figures for the SYSTEM class bar graphs are
constants, the figures for Free List Size and Modified List Size are
derived from the physical memory configuration and system parameters of
individual systems. The upper boundary figure for the Free List is the
number of pages available after deducting the pages permanently
allocated to the operating system. This figure, sometimes referred to
as balance set memory, is the number of pages that can
be allocated to processes, the Free List, and the Modified List. The
upper boundary figure for the Modified List is the value of the
MPW_HILIMIT system parameter. Note that both upper boundary figures are
calculated when the MONITOR request is initiated and do not change
thereafter.
Examples
| #1 |
MONITOR> MONITOR SYSTEM/ALL
OpenVMS Monitor Utility
SYSTEM STATISTICS
on node SAMPLE
29-APR-2000 12:43:28
CUR AVE MIN MAX
Interrupt Stack 0.33 0.33 0.33 0.33
MP Synchronization 0.00 0.00 0.00 0.00
Kernel Mode 0.16 0.16 0.16 0.16
Executive Mode 0.00 0.00 0.00 0.00
Supervisor Mode 0.00 0.00 0.00 0.00
User Mode 0.50 0.49 0.50 0.50
Compatibility Mode 0.00 0.00 0.00 0.00
Idle Time 99.00 98.67 99.00 99.00
Process Count 14.00 14.00 14.00 14.00
Page Fault Rate 0.33 0.33 0.33 0.33
Page Read I/O Rate 0.00 0.00 0.00 0.00
Free List Size 4255.00 4255.00 4255.00 4255.00
Modified List Size 105.00 105.00 105.00 105.00
Direct I/O Rate 0.00 0.00 0.00 0.00
Buffered I/O Rate 0.16 0.16 0.16 0.16
|
|
This example shows the tabular style format for the SYSTEM display.
| #2 |
MONITOR> MONITOR SYSTEM
Node: BRS004 OpenVMS Monitor Utility 5-JUN-2000 10:45:32
Statistic: CURRENT SYSTEM STATISTICS
Process States
+ CPU Busy (100) -+ LEF: 15 LEFO: 0
|**************************| HIB: 14 HIBO: 0
CPU 0 +--------------------------+ 100 COM: 8 COMO: 0
|* | PFW: 0 Other: 1
+--------------------------+ MWAIT: 0
Cur Top: BATCH_27 (6) Total: 38
+ Page Fault Rate (1438) -+ + Free List Size (35173) +
|****|*********************| |**************** | 54K
MEMORY 0 +--------------------------+ 500 0 +--------------------------+
|**** | |************* | 5765
+--------------------------+ + Mod List Size (3078) +
Cur Top: BATCH_29 (78)
+ Direct I/O Rate (442) -+ + Buffered I/O Rate (112) -+
|********************** | |***** |
I/O 0 +--------------------------+ 500 0 +--------------------------+ 500
|* | | |
+--------------------------+ +--------------------------+
Cur Top: BATCH_24 (23) Cur Top: BATCH_24 (6)
|
|
This example shows the bar graph style format for the SYSTEM display.
MONITOR TIMER
The MONITOR TIMER command initiates monitoring of the TIMER statistics
class, which is the rate of processing Timer Queue Entries (TQEs) by
the OpenVMS executive. A TQE is a data structure representing a timer
request made by a user or by the system.
Format
MONITOR TIMER
Command Qualifiers
/qualifier[,...]
One or more qualifiers as described in the Command Qualifier
Descriptions section.
Classname Qualifiers
/ALL
Specifies that a table of all available statistics (current, average,
minimum and maximum) is to be included in the display and summary
outputs. For summary output, this qualifier is the default for all
classes; otherwise, it is the default for all classes except CLUSTER,
MODES, PROCESSES, STATES, SYSTEM, and VECTOR.
/AVERAGE
Specifies that a bar graph of average statistics is to be included in
the display and summary outputs.
/CURRENT
Specifies that a bar graph of current statistics is to be included in
the display and summary outputs. The /CURRENT qualifier is the default
for the CLUSTER, MODES, STATES, SYSTEM, and VECTOR classes.
/MAXIMUM
Specifies that a bar graph of maximum statistics is to be included in
the display and summary outputs.
/MINIMUM
Specifies that a bar graph of minimum statistics is to be included in
the display and summary outputs.
Description
The TIMER class consists of the following data items, which are
displayed as rates of occurrences per second:
| Data Item |
Description |
|
Total TQE Rate
|
Total Rate of TQEs processed per second. This statistic is a combined
total of the three following TQE rates.
|
|
SYSUB TQE Rate
|
Rate of SYSUB TQEs processed per second. These system subroutine TQEs
represent timer requests made by the OpenVMS operating system.
|
|
Timer TQE Rate
|
Rate of Timer TQEs processed per second. These TQEs represent timer
requests made by users through the $SETIMR system service.
|
|
Wakeup TQE Rate
|
Rate of wakeup TQEs processed per second. These TQEs represent timer
requests made by users through the $SCHDWK system service.
|
Examples
| #1 |
MONITOR> MONITOR TIMER
OpenVMS Monitor Utility
TIMER STATISTICS
on node EBJB28
6-OCT-2000 08:46:13.84
CUR AVE MIN MAX
Total TQE Rate 56.00 56.00 56.00 56.00
SYSUB TQE Rate 51.33 51.33 51.33 51.33
Timer TQE Rate 4.33 4.33 4.33 4.33
Wakeup TQE Rate 0.33 0.33 0.33 0.33
|
|
This example shows a relatively low over-all level of TQE processing,
most of which has been requested by OpenVMS. Note that the last three
rates approximately total the first rate.
MONITOR TRANSACTION
The MONITOR TRANSACTION command initiates monitoring of the TRANSACTION
class, which shows information about transactions coordinated by DECdtm
services.
Format
MONITOR TRANSACTION
Command Qualifiers
/qualifier[,...]
One or more qualifiers as described in the Command Qualifier
Descriptions section.
Classname Qualifiers
/ALL
Specifies that a table of all available statistics (current, average,
minimum, and maximum) is to be included in the display and summary
output. For summary output, this qualifier is the default for all
classes; otherwise, it is the default for all classes except CLUSTER,
MODES, PROCESSES, STATES, SYSTEM, and VECTOR.
/AVERAGE
Specifies that a bar graph of average statistics is to be included in
the display and summary outputs.
/CURRENT
Specifies that a bar graph of current statistics is to be included in
the display and summary outputs. The /CURRENT qualifier is the default
for the CLUSTER, MODES, STATES, SYSTEM, and VECTOR classes.
/MAXIMUM
Specifies that a bar graph of maximum statistics is to be included in
the display and summary outputs.
/MINIMUM
Specifies that a bar graph of minimum statistics is to be included in
the display and summary outputs.
Description
The TRANSACTION class consists of the following data items:
| Data Item |
Description |
|
Start Rate
|
The rate at which new transactions are started on the local node.
|
|
Prepare Rate
|
The rate at which transactions on the local node are placed in the
Prepared state by DECdtm services.
|
|
One-Phase Commit Rate
|
The rate at which transactions on the local node complete using the
one-phase commit operation. This operation, which consumes
significantly fewer system resources, is used when there is only a
single resource manager participating in the transaction.
|
|
Total Commit Rate
|
The rate at which transactions on the local node are committed. This
value is the combined total of one-phase and two-phase commit
transactions.
|
|
Abort Rate
|
The rate at which transactions on the local node are aborted.
|
|
End Rate
|
The rate at which transactions that were started on the local node are
committed.
|
|
Remote Start Rate
|
The rate at which transaction branches are started on the local node.
|
|
Remote Add Rate
|
The rate at which transaction branches are added on the local node.
|
|
Completion Rate
|
The rate at which transactions complete, indexed by their duration in
seconds. The following list shows the Completion Rate categories:
|
Completion Rate 0--1
|
The number of transactions completed in 0--1 seconds (1 second or less)
|
|
Completion Rate 1--2
|
The number of transactions completed in 1--2 seconds
|
|
Completion Rate 2--3
|
The number of transactions completed in 2--3 seconds
|
|
Completion Rate 3--4
|
The number of transactions completed in 3--4 seconds
|
|
Completion Rate 4--5
|
The number of transactions completed in 4--5 seconds
|
|
Completion Rate 5+
|
The number of transactions that took more than 5 seconds to complete
|
For example, a transaction that completes in 0.5 second is included in the statistics displayed for the Completion Rate 0--1 category.
|
Examples
| #1 |
MONITOR> MONITOR TRANSACTION/ALL
OpenVMS Monitor Utility
DISTRIBUTED TRANSACTION STATISTICS
on node SAMPLE
16-JAN-2000 14:52:34
CUR AVE MIN MAX
Start Rate 34.76 34.76 34.76 34.76
Prepare Rate 33.77 33.77 33.77 33.77
One Phase Commit Rate 0.00 0.00 0.00 0.00
Total Commit Rate 35.09 35.09 35.09 35.09
Abort Rate 0.00 0.00 0.00 0.00
End Rate 35.09 35.09 35.09 35.09
Remote Start Rate 31.12 31.12 31.12 31.12
Remote Add Rate 31.45 31.45 31.45 31.45
Completion Rate 0-1 35.09 35.09 35.09 35.09
by Duration 1-2 0.00 0.00 0.00 0.00
in Seconds 2-3 0.00 0.00 0.00 0.00
3-4 0.00 0.00 0.00 0.00
4-5 0.00 0.00 0.00 0.00
5+ 0.00 0.00 0.00 0.00
|
|
This example shows the status of all transactions on node SAMPLE.
| #2 |
MONITOR> MONITOR TRANSACTION/MAXIMUM
OpenVMS Monitor Utility
+-----+ DISTRIBUTED TRANSACTION STATISTICS
| MAX | on node SAMPLE
+-----+ 16-JAN-2000 14:51:04
0 25 50 75 100
+ - - - - + - - - - + - - - - + - - - - -+
Start Rate 35 |**************
Prepare Rate 37 |**************
One Phase Commit Rate |
Total Commit Rate 35 |**************
Abort Rate |
End Rate 35 |**************
Remote Start Rate 33 |*************
Remote Add Rate 32 |************
| | | | |
Completion Rate 0-1 35 |**************
by Duration 1-2 |
in Seconds 2-3 |
3-4 |
4-5 |
5+ |
+ - - - - + - - - - + - - - - + - - - - -+
|
|
This example shows the maximum statistics of all transactions on node
SAMPLE.
|
