Document revision date: 30 March 2001 | |
![]() |
![]() ![]() ![]() ![]() |
![]() |
Previous | Contents | Index |
The MONITOR MSCP_SERVER command initiates monitoring of the mass storage control protocol (MSCP) server class.
MONITOR MSCP_SERVER
/qualifier[,...]
One or more qualifiers as described in the Command Qualifier Descriptions section.
/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.
The MSCP server class consists of the following data items that can be useful in tuning the MSCP server:
Data Item Description Server I/O Request Rate The rate at which remote processors request I/O transfers. Read Request Rate The rate at which remote processors request Read I/O transfers. Write Request Rate The rate at which remote processors request Write I/O transfers. Extra Fragment Rate The rate at which the server issues extra fragments. One or more extra fragments are created when, due to buffering constraints, the MSCP server issues multiple I/Os in order to fulfill a single I/O request. For example, if the MSCP server breaks up a 64-block request into 4 fragments of 16 blocks, 3 extra fragments are created. Fragmented Request Rate The rate at which fragmented requests occur. A fragmented request is a transfer request that the server fragments due to buffering constraints. For example, one fragmented request occurs when the server splits a 36-block request into 3 fragments of 16 blocks, 16 blocks, and 4 blocks. In this example, the server creates two extra fragments. Buffer Wait Rate The rate at which "buffer waits" occur in the server. A buffer wait occurs when a request must wait for MSCP buffer memory. Request Size Rates A histogram that displays the rate of requests for various block sizes.
MONITOR> MONITOR MSCP_SERVER
|
This example demonstrates use of the MONITOR MSCP_SERVER command to generate MSCP statistics on node GLOBBO.
The MONITOR PAGE command initiates monitoring of the PAGE class.
MONITOR PAGE
/qualifier[,...]
One or more qualifiers as described in the Command Qualifier Descriptions section.
/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.
The PAGE class includes the following data items:
Data Item Description Page Fault Rate Rate of page faults for all working sets Page Read Rate Rate of pages read from disk as a result of page faults Page Read I/O Rate Rate of read I/O operations from disk as a result of page faults Page Write Rate Rate at which pages were written to the page file Page Write I/O Rate Rate of write I/O operations to the page file Free List Fault Rate Rate at which pages were read from the free-page list as a result of page faults Modified List Fault Rate Rate of pages read from the modified-page list as a result of page faults Demand Zero Fault Rate Rate at which zero-filled pages were allocated as a result of page faults Global Valid Fault Rate Rate of page faults for pages that are not in the process's working set, but are in physical memory and are indicated as valid pages in the systemwide global page tables Writes In Progress Fault Rate Rate of pages read that were in the process of being written back to disk when faulted System Fault Rate Rate of page faults for pages in system space Free List Size Number of pages on the free-page list Modified List Size Number of pages on the modified-page list
MONITOR> MONITOR PAGE
|
This example shows that the current rate of pages read per read I/O operation is approximately 3 per second (Page Read Rate divided by Page Read I/O Rate). Note that while the page fault rate is currently at the highest point of the monitoring session, the majority of the pages are faulted from memory, not from disk.
The MONITOR PROCESSES command initiates monitoring of the PROCESSES class, which displays information about all processes in the system.In a multifile summary request, the classes CLUSTER and PROCESSES are ignored. If these classes are the only classes specified on the command line, MONITOR does not recognize them and displays a "no classes specified" error message.
MONITOR PROCESSES
/qualifier[,...]
One or more qualifiers as described in the Command Qualifier Descriptions section.
/TOPBIO
Specifies that a bar graph listing the top buffered I/O users be produced instead of the standard display and summary output. Values are expressed in units of buffered I/Os per second./TOPCPU
Specifies that a bar graph listing the top CPU time users be produced instead of the standard display and summary output. Values are expressed in units of clock ticks (10 milliseconds) per second.Prior to OpenVMS Version 7.3, the MONITOR PROCESSES/TOPCPU display showed only a maximum of 8 processes on one screen. In OpenVMS Version 7.3, the choice of which one of three screens is displayed is determined by the number of CPUs on the system. (See the examples in this section.)
/TOPDIO
Specifies that a bar graph listing the top direct I/O users be produced instead of the standard display and summary output. Values are expressed in units of direct I/Os per second./TOPFAULT
Specifies that a bar graph listing the top page faulting processes be produced instead of the standard display and summary output. Values are expressed in units of page faults per second./TOPRBS (VAX Only)
On OpenVMS VAX systems, specifies that a bar graph listing the top balance slot faulting processes be produced instead of the standard display and summary output. Values are expressed in units of balance slot faults per second.
As illustrated in the examples, the PROCESSES display (and summary) formats are different from those of all other classes. The PROCESSES display provides the following information:
Data Item Description PID Process identifier as assigned by the system, in hexadecimal STATE Process's scheduler state (see the description of the MONITOR STATES command for an explanation and a tabular summary of the STATES codes) PRI Current (as opposed to base) priority of the process NAME Process name PAGES Number of shareable pages and total number of pages currently in use by the process DIOCNT Cumulative direct I/O operations performed by the process since its creation; not displayed if the process is swapped out FAULTS Cumulative page faults since the process was created; not displayed if the process is swapped out CPU TIME Cumulative CPU time used by the process since its creation, in the format hours:minutes:seconds ; not displayed if the process is swapped out The top corners of the display contain the number of processes in the system and the time in days, hours, minutes, and seconds since the system was last booted. Processes that are swapped out are so noted.
If more processes are in the system than can be displayed on the terminal screen at once, the display consists of multiple screens. Screens are presented one at a time at intervals specified with the /VIEWING_TIME qualifier. The five /TOP bar graph displays provide the PID and process name of each of the top eight users.
As with the other bar graph displays, examples in the displays of top users are rounded to the nearest whole number. Up to eight processes with nonzero values are displayed. To be eligible for inclusion in the list of top users, a process must be present and swapped in at the beginning and end of the display interval. This eligibility requirement also applies to the beginning and ending of the entire period covered by a summary.
Note that only one of the displays of top users or the regular PROCESSES display can be selected in a single MONITOR request.
#1 | |
---|---|
MONITOR> MONITOR/INPUT=PROCS.DAT/INTERVAL=6 PROCESSES
|
This example illustrates a PROCESSES display generated from the input file PROCS.DAT. One line is displayed for each process in the system. This display shows current values only---average, minimum, and maximum statistics are not available. Also for swapped-out processes, the words SWAPPED OUT replace the three rightmost items, because those items are not available for swapped-out processes. Because this example is a playback request, the system uptime displayed is that of the system at the time the MONITOR data was recorded.
Nondisplayable characters in process names are represented by periods.
#2 | |
---|---|
MONITOR> MONITOR/INPUT=PROCS.DAT PROCESSES/TOPDIO
|
This example shows that the process SAMPLE0901, with a rate of 25 per second, was the top consumer of direct I/Os during the most recent interval between displays.
#3 | |
---|---|
MONITOR> MONITOR PROCESSES/TOPCPU
|
This example shows a MONITOR PROCESSES/TOPCPU screen display on a single CPU system.
#4 | |
---|---|
MONITOR> MONITOR PROCESSES/TOPCPU
|
This example shows s MONITOR PROCESSES/TOPCPU screen display on a 12-CPU system.
#5 | |
---|---|
MONITOR> MONITOR PROCESSES/TOPCPU
|
This example shows s MONITOR PROCESSES/TOPCPU screen display on a 16-CPU system.
Previous | Next | Contents | Index |
![]() ![]() ![]() ![]() |
privacy and legal statement | ||
6048PRO_044.HTML |