Reference
</br>
What it is
KPIs show user and traffic measurements for websites and applications, in order to best determine if they can withstand a certain amount of load to its backend servers. here are the 7 KPIs you need to know when you load test with JMeter:
Number of Users
To make sure websites can handle heavy loads created by the usage of many people, we simulate concurrent active users through virtual users. These virtual users act like “real” users on the website.
</br>
Hits per Second
Simulating the number of users can give us a good idea of the load, but it’s not by itself an accurate enough measurement. We also want to know how many requests are generated to the target server from users’ actions. Hits per second is the average number of samples initiated per second.
</br>
Errors per Second
The number of errors per second. A high Errors per Second rate can indicate a bottleneck that needs fixing before going live.
</br>
Response Time
This parameter measures** the amount of time it takes from the first byte of data to leave the user until the last byte is received by the user**.
</br>
Latency
The measurement of how long it takes from just before sending the request to just after receiving the first response. Part of the Response Time KPI, Latency helps us to measure and understand the inherent network delay during transmission of data from client to server.
</br>
Connect Time
The measurement of how long it takes the user to connect to the server, and the server to respond, including SSL handshake. It is a part of the Response Time KPI, and a part of the Latency KPI, but it is important for isolating SSL performance as a bottleneck.
</br>
Bytes/s (Throughput)
The measurement of the average bandwidth consumption that is generated by the test per second. This measures the amount of data flowing to and from the servers. Isolating this KPI is important for ensuring your network interface controllers are performing properly.
</br>
