LoadRunner: common Windows performance counters for load testing, analyzing server performance bottlenecks (1)

Document directory

• Monitored object

Monitored object ø System (system) l % Total processor time

Percentage of time when all processors in the system are busy. For a multi-processor system, this value can reflect the average busy status of all processors. The value is 100%, if half of the processors are busy, the value is 50% servers. Number of processors consumed by the server. If the server is dedicated to SQL Server, the maximum acceptable value is 80%-85%, which is a common CPU usage.

L file data operations/sec

The frequency at which the computer reads and writes the file system, but does not include file control operations.

L process Queue Length

The length of the queue to which the thread is waiting to allocate CPU resources. This length does not include threads that are occupying CPU resources. If the queue length is greater than the number of processors + 1, it indicates that the processor may be in a blocking state (reference value: <= number of processors + 1)

Ø processor (processor) l % processor time

CPU utilization. This counter is most commonly used. You can check whether the processor is saturated. If the value exceeds 95%, it indicates that the bottleneck of the current system is CPU, you can consider adding a processor or replacing a processor with better performance. (Reference Value: <80%)

L % priviliaged time

Percentage of time the CPU spends processing threads in privileged mode. General system services, city management, memory management, and other processes started by the operating system.

L % USER time

The opposite of the % privileged time counter refers to the percentage of time spent on operations in user State mode (that is, in non-privileged mode. If the value is large, you can consider whether to reduce the value through algorithm optimization or other methods. If the server is a database server, the reason for the large value is probably that database sorting or function operations consume too much CPU time. In this case, you can consider optimizing the database system. Indicates CPU-consuming database operations, such as sorting and executing Aggregate functions. If the value is very high, you can consider increasing the index and try to reduce the value by using simple table join and horizontal table segmentation methods.

L % DPC time

The time consumed by the processor in network processing. The lower the value, the better. The lower the value, the better. In a multi-processor system, if the value is greater than 50% and processor: % processor time is very high, adding a NIC may improve performance and the network provided is not saturated.

Ø memory (memory) l page faults/sec

When an error occurs when the processor reads a page in the memory, page failure occurs. If this page is located elsewhere in the memory, this error is called a soft error, measured by transition fault/sec. If this page is located on the hard disk, it must be re-read from the hard disk, which becomes a hard error. Hard errors will make the system run more efficiently soon. Page faults/sec: This counter indicates the number of error pages processed per second, including hard errors and soft errors.

L page input/sec

Number of pages written to the hard disk to solve the hard drive error (reference value:> = page reads/sec)

L page reads/sec

The number of pages read from the hard disk to solve the problem.

L page/sec

The number of pages read from or written to the hard disk to solve the hard drive error (reference value: 00 ~ 20)

L pages per second:

The number of pages retrieved per second. This number should be less than one working set per second: The Memory Page recently used by the thread, reflecting the number of memory pages used by each process. If the server has enough idle memory, the page will be left in the work set. When the free memory is less than a specific threshold, the page will be cleared from the working set.

L Available Mbytes

Remaining available physical memory, measured in megabytes (reference value:> = 10%. if the available Mbytes value is small (4 MB or smaller), the total memory on the computer may be insufficient, or a program does not release the memory.

L cathe bytes

File System cache (50% of available physical memory by default)

Ø process (process) l private bytes

The number of bytes that a process cannot share with other processes. When the counter value is large, it may be a memory leak signal.

L work set

Memory Page used by the latest processing thread

Physicaldisk (Disk) l % disk Time

Indicates the percentage of time the disk drive uses to provide services for read or write requests. If only % disk Time is large, the hard disk may be a bottleneck. The percentage of time the selected disk drive is busy providing services for read or write requests. If all three counters are large, the hard disk is not the bottleneck. If only % disk Time is large and both are moderate, the hard disk may be a bottleneck. Before recording this counter, run diskperf-YD in the command line window of Windows 2000. If the value exceeds 80%, the memory may leak. It should be less than 90%

L average disk Queue Length

Percentage of time used to provide services for Disk Read and Write requests. You can increase the disk array by adding a disk (<= twice the number of disks) the average number of Read and Write requests (queued for the selected disk at the instance interval. This value should not exceed 1.5 of the number of disks ~ 2 times. To improve performance, you can add disks. Note: A raid disk actually has multiple disks. The number of physical disks should not exceed 2 times. The normal value is <0.5

L average disk read Queue Length

Average number of disk read requests

L average disk write Queue Length

Average number of disk write requests

L average disk SEC/read

Average time of Data Reading on the disk, in seconds

L average disk SEC/transer

The average time of Data writing to a disk, in seconds. Generally, the value defined as less than 15 ms is the best, and the value between 15 and 30 ms is good, and the value between 30 and 60 ms is acceptable, if the disk size exceeds 60 ms, you need to consider replacing the hard disk or hard disk raid mode.

L % disk reads/sec (physicaldisk_total ):

Number of Hard Disk bytes read per second. This indicator should be smaller than the capacity of the disk I/O subsystem.

L % disk write/sec (physicaldisk_total ):

Number of Hard Disk bytes written per second. This indicator should be smaller than the capacity of the hard disk I/O subsystem.

L disk Bytes/sec

The Byte rate transmitted or transferred from the disk during write or read operations.
This value depends on the hard disk speed.

L disk transfers/sec

The read/write operation rate on this disk.
Normal value <(DiskBytes/Sec)/3. If the value is too large, it indicates the value required by the system.IoThe speed is close to the maximum speed of the hard disk. d

Network Interface (network) l byte total/sec

Indicates the speed at which bytes are received and sent in the network. You can use this counter to determine whether the network has a bottleneck (reference value: This counter is different from the network bandwidth, <50%)