Average transaction response times Average transation Response time
Excellent: <2s
Good: 2-5s
Pass: 6-10s
failed: >10s
Hits per second Hits per Second
When increasing the pressure of the system (or increasing the number of concurrent users), the throughput rate and the TPS change curve is generally consistent, the system is basically stable, if the pressure increases, the throughput curve increases to a certain degree after the change is slow, even flat, it is likely that the network bandwidth bottleneck; A slow or flat change in the TPS curve indicates that the server is starting to bottleneck.
Request response time to last Byte
System processing transactions per second Transaction per second
Throughput Throughout
good: 70%
bad: 85%
poor: 90%+
CPU time consumed by database operations Processor/%user times
If the value is large, consider whether the value can be lowered by means of a friendly algorithm. If the server is a database server, the reason why the Processor\%user time value is large is likely to be that the database is sorted or the function operation consumes too much CPU, so you can consider optimizing the database system.
CPU Average utilization processor/%privileged time
If the parameter value and the "physical Disk" parameter values are always high, there is a problem with I/O. Consider replacing a faster hard drive system.
The remaining available memory memory/avaiable Mbytes
At least 10% of the physical memory value is needed.
Physical Disk utilization physical Disk/%disk time
good: <30 %
bad:< 40%
NET Throughput Network Interface/bytes total/sec
Determine if the network connection speed is a bottleneck, you can use the value of this counter and the current network bandwidth, the results should be less than 50%.
This article is from the Ivy blog, so be sure to keep this source http://zqivy.blog.51cto.com/4934723/1928902
LoadRunner Detecting Windows Resource counter requirements