Share this page

# System Resources graphs

The System Resources graphs display the system resources usage measured by the online monitors during the load test scenario run. These graphs require that you specify the resources you want to measure before running the scenario. For more information, see System Resource monitoring in the Controller documentation.

In this topic:

## Host Resources graph

The Host Resources graph helps you determine the impact of Vuser load by displaying a summary of the System Resources usage for each Windows based OpenText Enterprise Performance Engineering host (Controller and load generators) measured during the load test scenario.

Axis | Description
--- | ---
X-axis | Elapsed time since the start of the run.
Y-axis | The usage of resources on the Windows hosts.

In a typical example, you can see a peak in the usage of Disk Time and Processor Time as the Memory Usage decreases towards the end of the load test.

## SNMP Resources graph

The SNMP Resources graph shows statistics for machines running an SNMP agent, using the Simple Network Management Protocol (SNMP).

Note: To obtain data for this graph, you need to enable the SNMP monitor (from Controller) and select the default measurements you want to display, before running the scenario.

Axis | Description
--- | ---
X-axis | Elapsed time since the start of the run.
Y-axis | The usage of resources on a machine running the SNMP agent.

In a typical example, SNMP measurements are displayed for each machine.

## Sitescope graph

The Sitescope graph shows network and processor performance measurements. For detailed information on the performance counters, refer to the SiteScope documentation and SiteScope server monitoring.

## UNIX Resources graph

The UNIX Resource graph helps you determine the impact of Vuser load on the various system resources by displaying the UNIX resources measured during the load test scenario. The UNIX measurements include: average load, collision rate, context switch rate, CPU utilization, incoming packets error rate, incoming packets rate, interrupt rate, outgoing packets error rate, outgoing packets rate, page-in rate, page-out rate, paging rate, swap-in rate, swap-out rate, system mode CPU utilization, and user mode CPU utilization.

Note: To obtain data for this graph, select the measurements for the online monitor (from Controller) before running the scenario.

Axis | Description
--- | ---
X-axis | Elapsed time since the start of the run.
Y-axis | The usage of resources on the UNIX machine.

### UNIX Resources Default Measurements

The following default measurements are available for UNIX machines:

Measurement | Description
--- | ---
Average load | Average number of processes simultaneously in `Ready' state during the last minute.
Collision rate | Collisions per second detected on the Ethernet.
Context switches rate | Number of switches between processes or threads, per second.
CPU utilization | Percent of time that the CPU is utilized.
Disk rate | Rate of disk transfers.
Incoming packets error rate | Errors per second while receiving Ethernet packets.
Incoming packets rate | Incoming Ethernet packets per second.
Interrupt rate | Number of device interrupts per second.
Outgoing packets errors rate | Errors per second while sending Ethernet packets.
Outgoing packets rate | Outgoing Ethernet packets per second.
Page-in rate | Number of pages read to physical memory, per second.
Page-out rate | Number of pages written to pagefile(s) and removed from physical memory, per second.
Paging rate | Number of pages read to physical memory or written to pagefile(s), per second.
Swap-in rate | The rate by which disk content is swapped into the machine's memory in kBps.
Swap-out rate | The rate by which the machine's memory is being swapped out to disk in kBps.
System mode CPU utilization | Percent of time that the CPU is utilized in system mode.
User mode CPU utilization | Percent of time that the CPU is utilized in user mode.

## Windows Resources graph

The Windows Resources graph helps you determine the impact of Vuser load on the Windows resources measured during the load test scenario. The Windows measurements correspond to the built-in counters available from the Windows Performance Monitor.

Note: To obtain data for this graph, select the measurements for the online monitor (from Controller) before running the scenario.

Axis | Description
--- | ---
X-axis | Elapsed time since the start of the run.
Y-axis | The usage of resources on the Windows machine running the load test scenario.

### Windows Resources Default Measurements

The following default measurements are available for Windows Resources:

Object | Measurement | Description
--- | --- | ---
System | % Total Processor Time | The average percentage of time that all the processors on the system are busy executing non-idle threads. On a multi-processor system, if all processors are always busy, this is 100%, if all processors are 50% busy this is 50% and if 1/4 of the processors are 100% busy this is 25%. It can be viewed as the fraction of the time spent doing useful work. Each processor is assigned an Idle thread in the Idle process which consumes those unproductive processor cycles not used by any other threads.
Processor | % Processor Time | The percentage of time that the processor is executing a non-idle thread. This counter was designed as a primary indicator of processor activity. It is calculated by measuring the time that the processor spends executing the thread of the idle process in each sample interval, and subtracting that value from 100%. (Each processor has an idle thread which consumes cycles when no other threads are ready to run.) It can be viewed as the percentage of the sample interval spent doing useful work. This counter displays the average percentage of busy time observed during the sample interval. It is calculated by monitoring the time the service was inactive, and then subtracting that value from 100%.
System | File Data Operations/sec | The rate at which the computer issues read and write operations to file system devices. This does not include File Control Operations.
System | Processor Queue Length | The instantaneous length of the processor queue in units of threads. This counter is always 0 unless you are also monitoring a thread counter. All processors use a single queue in which threads wait for processor cycles. This length does not include the threads that are currently executing. A sustained processor queue length greater than two generally indicates processor congestion. This is an instantaneous count, not an average over the time interval.
Memory | Page Faults/sec | This is a count of the page faults in the processor. A page fault occurs when a process refers to a virtual memory page that is not in its Working Set in the main memory. A page fault does not cause the page to be fetched from disk if that page is on the standby list (and hence already in main memory), or if it is in use by another process with which the page is shared.
PhysicalDisk | % Disk Time | The percentage of elapsed time that the selected disk drive is busy servicing read or write requests.
Memory | Pool Nonpaged Bytes | The number of bytes in the non-paged pool, a system memory area where space is acquired by operating system components as they accomplish their appointed tasks. Non-paged pool pages cannot be paged out to the paging file. They remain in main memory as long as they are allocated.
Memory | Pages/sec | The number of pages read from the disk or written to the disk to resolve memory references to pages that were not in memory at the time of the reference. This is the sum of Pages Input/sec and Pages Output/sec. This counter includes paging traffic on behalf of the system cache to access file data for applications. This value also includes the pages to/from non-cached mapped memory files. This is the primary counter to observe if you are concerned about excessive memory pressure (that is, thrashing), and the excessive paging that may result.
System | Total Interrupts/sec | The rate at which the computer is receiving and servicing hardware interrupts. The devices that can generate interrupts are the system timer, the mouse, data communication lines, network interface cards, and other peripheral devices. This counter provides an indication of how busy these devices are on a computer-wide basis. See also Processor:Interrupts/sec.
Objects | Threads | The number of threads in the computer at the time of data collection. Notice that this is an instantaneous count, not an average over the time interval. A thread is the basic executable entity that can execute instructions in a processor.
Process | Private Bytes | The current number of bytes that the process has allocated that cannot be shared with other processes.

## See also

- Windows Resources monitor

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 26.1-26.3 All View Local Help Center View Online Help Center Version: