0% found this document useful (0 votes)
65 views

Performance Test Monitoring

This document provides counters and metrics for monitoring processor, memory, disk, and network utilization on a system. It includes percentages for processor utilization broken down by user time, kernel time, and I/O wait. It also includes counts of interrupts, context switches, available memory, page faults, disk queue length, bytes sent and received on the network. High or consistent values for some of these metrics like processor queue length, page faults, disk queue length may indicate performance bottlenecks that require further investigation.

Uploaded by

Karan Dahda
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
65 views

Performance Test Monitoring

This document provides counters and metrics for monitoring processor, memory, disk, and network utilization on a system. It includes percentages for processor utilization broken down by user time, kernel time, and I/O wait. It also includes counts of interrupts, context switches, available memory, page faults, disk queue length, bytes sent and received on the network. High or consistent values for some of these metrics like processor queue length, page faults, disk queue length may indicate performance bottlenecks that require further investigation.

Uploaded by

Karan Dahda
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Counter Processor Counters

% Processor Utilization

Identifier
Processor_Total: % Processor Time Processor_Total: % User Time Processor_Total: % Privilege Time

% User time

% Privileged time

% I/O Wait

%wio - in case of UNIX platforms Processor Queue Length System: Processor Queue Length

Interrupts per second Context Switches

Processor: Interrupts per second System: Context Switches per second

Memory Counters
Available Memory Pages per second Memory: Available Mbytes Memory: Pages/sec

Page Faults per second

Memory: Page Faults/sec

Process Memory Page Reads/sec Memory Page Writes/sec

Process: Working Set Memory Page Reads/sec Memory Page Writes/sec

Disk Counters
% Disk Utilization Physical Disk: % Disk Time Disk Queue Length Physical Disk: Average Disk Queue length Average Disk Read queue Physical Disk: Average length Disk Read queue length

Average Disk Write queue Physical Disk: Average length Disk Write queue length Average Disk sec/Transfer Disk Reads/sec Physical Disk: Average Disk sec/Transfer Logical Disk: Disk Reads/sec

Network Counters
Total Bytes Bytes Sent Bytes Received Network Interface: Bytes Total/sec Network Interface: Bytes Sent/sec Network Interface: Bytes Received/sec

Description
This counter helps in knowing how busy the system is. It indicates the processor activity. It is the average percentage of elapsed time that the processor spends to execute a productive (non-idle) thread. This refers to the processors time spent in handling the application related processes. This refers to the processors time spent in handling the kernel mode processes.

This refers to the percentage wait for completion of I/O activity. This counter helps in identifying how many threads are waiting in queue for execution. A consistent queue length of more than 2 indicates bottleneck and it is worth investigation. Interrupts per second refers to the number of interrupts that the hardware devices sends to the processor. Context Switches refers to the switching of the processor from a lower priority thread to a high priority thread.

This indicates the amount of free available memory. This counter is the best indicator memory shortage problems.. It indicates the number of pages stored/retrieved from the secondary memory (disk) due to paging. This counter provides the count of how many times the information was not available in the primary memory location where it was expected to be. This includes the count of soft page faults/sec (available at different location in the primary memory) and hard page faults/sec (available in the disk). This counter provides the instance level (process) memory information of which process takes more primary memory (RAM).

This counter provides a clear indication how much busy is disk. This counter is a clear indicator of disk issues.

This counter refers to the total number of bytes sent and received at any point of time. This refers to the total number of bytes sent to the NIC at any point of time. This refers to the total number of bytes of incoming traffic received by the NIC at any point of time.

Comments
A consistent level of more than 80% utilization (in case of single CPU machines) indicates that there is not enough CPU capacity. It is worth further investigation using other processor counters. A high percentage indicates that the application is consuming high CPU. The process level counters needs to be monitored to understand which user process consumes more CPU. A high value indicates that the processor is too busy in handling other operating system related activities. It needs immediate attention from the system administrator to check the system configuration or service. It is a good indication to confirm whether the threads are waiting for the I/O completion. Generally if the queue length is more than the number of CPUs available in the system, then it might reduce the system performance. A high value of % usr time coupled with high processor queue length indicates the processor bottleneck. A consistent value of above 1000 in Interrupts per second indicates hardware failure or driver configuration issues. A consistent value of above 15000 per second per processor indicates the presence of too many threads of same priority and possibility of having blocked threads.

A consistent value of less than 20% of RAM indicates the memory problem as per Microsoft standards. A consistent value of more than 5 indicates the memory problem.

A consistent high Hard Page faults/sec value indicates the memory shortage problem. A high Page Faults/sec value coupled with high Memory: Pages/sec indicates the shortage of memory.

The working set refers to the number of pages that a process can address in the primary memory without causing a paging.

A consistent value of more than the number of spindles plus two indicates waiting threads for disk.

A consistent value of more than 80% of the network bandwidth indicates the problem.

You might also like