G.4 E . . . H . . . I . . . L

Event Monitor
A component of the Capacity Planner software that collects additional event-based data for capacity planning.
.EVM file
A collection of binary event data produced by the Event Monitor; also called the event data file.
hard page fault
Each time a process references a virtual page that is not in its working set and requests a read from disk, a hard page fault is generated.

A page fault results in disk I/Os. Such I/Os are known as fault I/Os.

Compare with soft page fault.

inactive process
A process that uses no system resources during the analysis period, except some memory. The PerfCap Capacity Planner places inactive processes in class 0, which is then discarded or ignored.
interactive process
Classification for any process (regardless of process type) with an interactive transaction.

Subprocesses that do interactive work are reclassified as interactive.


Note
OpenVMS Only

This reclassification may also occur for detached processes. A batch job issuing a broadcast message is not classified as interactive.

interactive transaction
A think- and response-time pair.

For other interactive transactions, such as those that occur within editors, an interactive transaction may consist of a single keystroke or a complete editor command. For example, every keystroke on input is an interactive transaction; an editor FIND command is an interactive transaction.

In MAIL, a SEND command is terminated when the TO: prompt appears, signifying the completion of one interactive transaction and the start of another. With the SEND/EDIT command, every character entered is an interactive transaction.

An interactive transaction is defined as any keyboard sequence (one or more commands or keystrokes) that results in consumption of CPU and other system resources. Typical examples are commands (terminated by pressing the Return key) and editing keystrokes. A transaction is a response and think time pair.

The relationship between transaction, response time, and think time is illustrated in the Figure, Response Time, Think Time, and Transaction.

The first RETURN (far left) indicates the end of input (for example, the terminator for the last command, an editor prompt, or a cursor flash); the dollar prompt indicates that the system has processed the command and is ready for further input; while the last (far right) RETURN indicates the end of the next input (for example, the terminator for the next command). This diagram is specifically geared toward DCL commands; in an editor, the end of a command is any keystroke or escape sequence.

Reaction time is not measured by the PerfCap Capacity Planner (time from end of input to display of first response character from system). Think time includes time spent by the terminal user in thinking about the previous output, determining what to do next, and in typing the next command. Since a portion of think time is spent in examining the previous output, a transaction is depicted as a response- and think-time pair rather than a think- and response-time pair.

See also response time and think time.


Note
OpenVMS

interrupt stack
The average percentage of CPU time spent servicing device interrupts for processes on the local node for the measurement interval.
LAN
Local area network.
.LOG file
A batch process record produced by the Event Monitor; also called a log file.


Previous Page | Next Page | Table of Contents