LoadRunner Performance Test Index Analysis

Object	Counters	Descr resume ption	Reference Value
Memory	Available Mbytes	Number of available physical memory. 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.	4 MB or smaller, with at least 10% physical memory value
	Page/sec (Input/out)	The number of pages retrieved or written from the disk to resolve hard page errors. Generally, if the page/sec continues to exceed several hundred, you should study the page exchange activity further. You may need to increase the memory to reduce the page feed requirement (you can multiply this number by 4 K to get the hard disk data traffic caused by this ). A large value of pages/sec does not necessarily indicate memory problems, but may be caused by running programs that use memory ing files.	Recommended 00-20 If the server does not have enough memory to handle its workload, this value will remain high. If it is greater than 80, it indicates that there is a problem (too many read/write operations need to access the disk, you can consider increasing the memory or optimizing the data read/write algorithm ). The value of this series of counters is relatively low, indicating that the response request is faster. Otherwise, it may be caused by a shortage of memory in the server system (or because the cache is too large, resulting in too little system memory ).     > 5. The lower the value, the better.
	Page Fault	Error pages processed by the processor per second (including soft/hard errors ). When the processor requests a page (which may be data or code) at a specified location in the memory, this constitutes a page fault. If the page is located elsewhere in the memory, this error is called a soft error (measured by the transition fault/sec stenographer). If the page must be re-read from the hard disk, it is called a hard error. Many processors can continue to operate in the case of a large number of soft errors. However, hard errors can cause significant delays.
	Page input/sec	The number of pages read from the disk to solve the hard error page.
	Page output/sec
	Page reads/sec	The number of times a hard error page is read from the disk. Resolution of memory references, the number of times page files must be read. The threshold value is greater than 5. The lower the threshold, the better. A large value indicates disk read rather than cache read.
	Cache bytes	File System cache. By default, 50% of the available physical memory is used. If the iis5.0 runtime memory is insufficient, it will automatically sort out the cache. Pay attention to the trend changes of this counter
	Memory leakage	If you suspect Memory leakage, Please monitor memory // available bytes and memory // committed bytes to observe memory behavior, and monitors the process/private bytes, process // working set, and process // handle count that may leak the memory. If you suspect that a kernel-mode process causes leakage, you should also monitor memory/pool nonpaged bytes, memory // pool nonpaged allocs and process (process_name) // pool nonpaged bytes.
Process	Page faults/sec	Compare the page faults generated by the process with those generated by the system to determine the impact of the process on the system page faults.
	Private bytes	The number of current bytes allocated by this process that cannot be shared with other processes. If the system performance decreases over time, this counter can be the best indicator of Memory leakage.
	Work set	The memory page recently used by the processing thread 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.
Processor	% Processor time	Number of consumed CPU time. If the server is dedicated to SQL Server, the maximum acceptable upper limit is 80%-85%, which is a common CPU usage.
	Processorqueue Length	Determine the CPU bottleneck. If the length of the queue displayed by processor queue length remains unchanged (> = 2) and the processor utilization % processor time exceeds 90%, there may be a processor bottleneck. if the length of the processor queue is found to exceed 2, but the processor utilization is always very low, it may be better to solve the problem of processor congestion. Here, the processor is generally not a bottleneck.
Physical Disk	% Disktime	The percentage of time the selected disk drive is busy providing services for read or write requests. Normal value <10. If this value is too large, it takes too much time to access the disk. You can consider increasing the memory, replacing the hard disk faster, and optimizing the read/write algorithms. If the value exceeds 80 (the processor and network connection are not saturated at this time), memory leakage may occur.
	Currentdiskqueuelength	The average number of Read and Write requests (queued for the selected disk at the instance interval. (1.5-2 times the number of disks)
	AVG. Disk queue Length AVG. Disk Read Queuelength AVG. disk write Queuelength Disk Read/sec Disk write/sec	The average number of Read and Write requests (queued for the selected disk at the instance interval. Formula for determining disk bottleneck: The number of I/O per disk = (read count + (4 * write count)/number of disks. If the number of I/O operations on each disk is greater than that of the disk, the disk has a bottleneck.	AVG. diskqueue length normal value <0.5. If this value is too large, it indicates that the disk Io is too slow and the hard disk needs to be replaced faster.