Shulou(Shulou.com)05/31 Report--

Today, I will talk to you about what the common Web server performance indicators are, which may not be well understood by many people. In order to make you understand better, the editor has summarized the following contents for you. I hope you can get something according to this article.

As IT personnel, maintaining the web server is a common task. Generally, if we do not plan in detail, or use relevant software, it is inefficient to judge work efficiency purely by the stability of the system, so some common performance indicators are listed and discussed below.

1. Transaction (Transaction)

In the web performance test, a transaction represents a process of "sending a request from the user-> web server receiving the request, processing-> web server getting data from DB-> generating the user's object (page) and returning it to the user". The general response time is for the transaction.

two。 Request response time

Request response time refers to the time taken from a request initiated by the client to the end when the client receives the response returned from the server. In some tools, the response is often referred to as "TTLB", or "time to last byte", which means the time it takes from initiating a request to receiving an one-byte response from the client. The unit of response time is generally "seconds" or "milliseconds". A formula can say: response time = network response time + application response time. The standard can refer to the foreign principles of 3-5-10:

(1) within 3 seconds, the page responds to the user and displays it, which can be considered "very good".

(2) within 3-5 seconds, the page responds to the user and displays it, which can be considered "good".

(3) within 5-10 seconds, the page responds to the user and displays it, which can be regarded as "reluctantly accepted".

(4) it makes people a little impatient after more than 10 seconds, and users are likely not to wait any longer.

3. Transaction response time

The transaction may consist of a series of requests, and the response time of the transaction is mainly for the user, which belongs to the macro concept and is proposed to explain the business response time to the user. For example, the response time of an interbank withdrawal transaction consists of a series of requests. Transaction response time is a parameter that directly measures the performance of the system.

4. Number of concurrent users

Concurrency is generally divided into two cases. One is concurrency in the strict sense, that is, all users do the same thing or operation at the same time, which generally refers to doing the same type of business. For example, in the credit card examination and approval business, a certain number of supporters submit the completed examination and approval business at the same time; there is another special case, that is, all users perform exactly the same operation, for example, in the credit card examination and approval business, all users can apply for business together, or modify the same record.

Another type of concurrency is concurrency in a broad range. The difference between this concurrency and the previous concurrency is that although multiple users have made requests or operations on the system, these requests or operations can be the same or different. For the whole system, there are still many users operating on the system at the same time, so it also belongs to the category of concurrency.

As you can see, the latter concurrency includes the former concurrency. And the latter kind of concurrency is closer to the actual use of users, so for most systems, only a small number of users carry out "strict concurrency". For WEB performance testing, these two concurrency situations generally need to be tested, and the usual practice is to conduct a strict sense of concurrency testing first. Strictly speaking, user concurrency generally occurs in frequently used modules, although the probability of occurrence is not very high, but once a performance problem occurs, the consequences are likely to be fatal. In a strict sense, concurrent testing is often associated with functional testing, because exceptions to concurrent functions are usually a program problem, and this kind of testing is also part of robustness and stability testing.

Number of user concurrency: there are two common misconceptions about the number of user concurrency. One wrong view is to understand the number of concurrent users as the number of all users using the system, on the grounds that these users may use the system at the same time; and a closer to the correct view is to understand the number of online users as the number of concurrent users. In fact, online users do not necessarily have concurrency with other users, such as those who are browsing web pages, which does not have any impact on the server. However, the number of online users is one of the main bases for calculating the number of concurrent users.

5. Throughput

Refers to the sum of the amount of data transmitted on the network during a performance test. Throughput / transmission time is throughput.

6. TPS (transactionper second)

The number of transactions or transactions that the system can handle per second. It is an important index to measure the processing ability of the system.

7. Click rate

The number of HTTP requests submitted by the user to the WEB server per second. This indicator is a unique indicator of WEB applications: WEB applications are "request-response" mode, and the server will process every request made by the user, so click is the smallest unit of transactions that can be processed by WEB application. If each click is defined as a transaction, click-through rate and TPS are the same concept. It is easy to see that the greater the click-through rate, the greater the pressure on the server. Click-through rate is only a reference index for personality, and it is important to analyze the impact of click-through. It should be noted that the click here does not refer to a single click of the mouse, because the client may issue multiple HTTP requests to the server in a single click.

8. Resource utilization ratio

Refers to the use of different system resources, such as server CPU utilization, disk utilization, etc. Resource utilization is the main basis for analyzing system performance index and improving system performance, so it is the focus of WEB performance testing.

Resource utilization is mainly aimed at WEB server, operating system, database server, network and so on, which is the main reference for testing and analyzing bottleneck. In the WEB performance test, the corresponding parameters are collected and analyzed according to the need.

Here are some common test metrics

Web server metrics

Database server performance metrics

Bottleneck definition of the system

Stabilize the resource state of the system

After reading the above, do you have any further understanding of the common Web server performance metrics? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.