LoadRunner Windows counters

Object Object	Counters (Counter name)	Description Description	Reference values
Memory	Available Mbytes	The number of physical memory available. If the value is small (4MB or less), the total memory on the computer may be insufficient, or a program does not release memory. Each additional connection will occupy around 10KB on this basis	At least 10% of the physical memory value
Memory	Page/sec	Indicates the number of pages fetched from disk because of a page error, or a page that was written to disk to free the workspace due to a page error	Recommended value is 0~20, generally if the value continues above hundreds of, then the paging activity should be studied further
Memory	Page read/sec	Number of pages read per second	The threshold value is 5, the lower the better, the larger the threshold value is read from disk rather than from the cache
Memory	Page faults/sec	Number of failed pages per second (including soft and hard failure)
Memory	Cache Bytes	FileSystem caching (file system cache)	The available physical memory is 50% by default. If IIS5.1 runs out of memory, it automatically organizes the memory. You need to focus on the trend change of the counter.
Memory	Pages per second	Number of pages retrieved per second	Should be less than one page per second
Process	%processor time	CPU usage, viewing processor saturation	Less than 75%
Process	%user time	Represents CPU-intensive database operations such as sorting, execution, aggregate functions, etc.	If the value is high, consider increasing the index, using simple table joins, and horizontally splitting large tables to reduce the value
Process	%priviledged time	(CPU core time) Percentage of time spent in a privileged mode to process thread execution code	If the value and the physical disk parameter values are always high, there is a problem with I/O. Consider replacing a faster disk system
Process	Processor Queue Length	The instantaneous length of the processor queue, in number of long-range units
process	DPC time		To determine CPU bottlenecks, if the queue length shown by the Processor queue remains constant (greater than or equal to 2) and the processor utilization%processor time exceeds 90%, there is likely a processor bottleneck
Thread	Contextswitches/sec	Instantiate the Inetinfo and dllhost processes, and if you want to increase the size of the thread bytes pool, you should monitor these three counters. Increasing the number of threads may increase the number of context switches so that performance does not rise instead of falling. If the context switch value for 10 instances is very high, you should reduce the size of the thread byte pool
Physical Disk	%disk time	Refers to the percentage of time that the selected disk drive has served to read or write requests	The normal value is less than 10, which means too much time to access the disk, consider increasing memory, replacing faster drives, and optimizing the algorithms for reading and writing data
Physical Disk	Avg.Disk quequ Length	Refers to the average number of read and write requests that are queued in the instance interval for the selected disk.	Normal value is less than 0.5, this value is too large to indicate that disk I/O is too slow to replace a faster hard disk
Physical Disk	Current Disk Queqe Length	The current number of requests on the disk when performance data is collected, and it also includes requests that are in service at the time of collection. This is an instantaneous snapshot, not an average. A multi-axis disk device can have multiple requests that are in a running state, but other concurrent requests are waiting for service

LoadRunner Windows counters