LoadRunner Index Analysis

We need to monitor the CPU, memory, and hard disk resources. The following parameters are provided for analysis.
% Processor time (processor_total): number of processors consumed by the server. If the server is dedicated to SQL Server, the maximum acceptable upper limit is 80%-85%, which is the common CPU usage.
% USER time (processor_total): 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.
% DPC time (processor_total): the lower 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.
% Disk Time (physicaldisk_total): the percentage of time the selected disk drive was 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.
Availiable bytes (memory): number of physical memories used. If the available Mbytes value is small (4 MB or smaller), it indicates that the total memory on the computer may be insufficient or a program has not released the memory.
Context switch/sec (system): (instantiate inetinfo and DLLHOST processes) if you decide to increase the size of the thread's byte pool, you should monitor these three counters (including the one above ). Increasing the number of threads may increase the number of context switches, so that the performance will not increase but decrease. If the context switching value of the ten instances is very high, the size of the thread byte pool should be reduced.
% Disk reads/sec (physicaldisk_total): number of Hard Disk bytes read per second.
% Disk write/sec (physicaldisk_total): number of Hard Disk bytes written per second.
Page faults/sec: Compare page faults generated by a process with those generated by the system to determine the impact of the process on system page faults.
Pages per second: the number of pages retrieved per second. The number should be less than one page per second
Working Set: The Memory Page recently used by the thread, which reflects 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.
AVG. Disk queue length: the average number of Read and Write requests (queued for the selected disk in 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.
Average disk read/write queue length: the average number of read (write) requests (queues)
Disk reads/(writes)/S: Number of disk reads and writes on the disk per second. The sum of the two should be less than the maximum capacity of the disk device
Quantity.
Average disk SEC/read: the average time required to read data on this disk in seconds.
Average disk SEC/transfer: the average time required to write data to this disk in seconds.
Bytes total/sec: the speed at which bytes are sent and received, including frame characters. Determine whether the network connection speed is a bottleneck. You can use the counter value to compare with the current network bandwidth.
Page read/sec: Number of physical database page reads per second. This statistics shows the total number of physical pages read between all databases. Because of the high overhead of physical I/O, you can minimize the overhead by using larger data caching, smart indexing, more efficient queries, or changing database design.
Page write/sec: (write page/second) Number of pages written by the physical database per second.

LoadRunner Index Analysis