Collation of Web Performance Testing terms

Concurrent users:

Concurrency is generally divided into two types. One is strict concurrency, that is, all users perform the same thing or operation at the same time. This operation generally refers to the same type of business. For example, in the Credit Card Approval business, a certain number of users submit completed approval services at the same time. There is also a special case that all users perform identical operations, for example, in the Credit Card Approval business, all users can apply for the business together or modify the same record. Another concurrency is concurrency in a broad range. The difference between this concurrency and the former concurrency is that although multiple users send requests or perform operations to the system, these requests or operations can be the same or different. For the entire system, there are still many users operating on the system at the same time, so it is also in the scope of concurrency.
We can see that the latter concurrency includes the former. In addition, the latter type of concurrency is closer to the actual usage of users. Therefore, for most systems, only a few users can perform "strict concurrency ". For Web performance testing, the two concurrency situations generally require testing. The common practice is to perform a strict concurrency test first. Strictly speaking, user concurrency generally occurs in frequently-used modules. Although the probability of occurrence is not very high, once a performance problem occurs, the consequences may be fatal. Strictly speaking, concurrent tests are often associated with functional tests, because exceptions in concurrent functions are usually causedProgramProblem: This test is also part of the robustness and stability test.

Concurrent user count:

The number of concurrent requests refers to the number of customers simultaneously. There are two common errors about the number of concurrent users. An incorrect idea is to regard the number of concurrent users as the number of all users who use the system, on the grounds that these users may use the system at the same time; another idea is to regard the number of online users as the number of concurrent users. In fact, online users may not be concurrent with other users. For example, users who are browsing the Web page have no impact on the server. However, the number of online users is one of the main bases for calculating the number of concurrent users.

Request Response Time:

It refers to the time when the client sends a request to get a response. In some tools, the request response time is usually "tllb", that is, "Time to last byte", which means starting from initiating a request, it takes time for the client to receive the response of the last byte. The unit of the request response time is generally "seconds" or "milliseconds ".

Transaction Response Time:

A transaction may be composed of a series of requests. The response time of a transaction is mainly for users. It is a macro concept and is proposed to explain the business response time to users. for example, the response time of a interbank withdrawal transaction is composed of a series of requests. the transaction response time and subsequent service throughput are parameters that directly measure system performance.

Throughput:

This refers to the total amount of data transmitted over the network during one-time testing. throughput/transmission time is the throughput.

TPS:

Transaction per second is the number of transactions or transactions that the system can process per second. It is an important indicator to measure the processing capability of the system.

Click rate:

HPS, the number of HTTP requests that the user submits to the Web server per second. this metric is a unique indicator of a Web application: the Web application is in the "request-response" mode, and the server processes an application once, therefore, clicking is the smallest unit of transactions that Web applications can process. if you define each click as a transaction, click rate and TPS are one concept. it is easy to see that the higher the click rate, the more pressure on the server. click-through rate is only a performance reference indicator. It is important to analyze the impact of clicks. Note that clicking here does not mean one click operation with the mouse, because in one click operation, the client may send multiple HTTP requests to the server.

Resource Utilization:

It refers to the usage of different system resources, such as the CPU utilization and disk utilization of the server. resource utilization is the main basis for analyzing system performance indicators and improving performance. Therefore, it is the focus of Web performance testing. resource Utilization mainly targets Web servers, operating systems, database servers, and networks. It is a major reference for testing and analyzing bottlenecks. in Web performance testing, relevant parameters are collected as needed for analysis.