Performance test process (three)-analysis test points

After you understand your system architecture, you can analyze the performance test points next. Because this is related to the selection of your test tool.

Selection of performance test points

* Frequent occurrences (for example: login, sending and receiving mail in a certain mailbox core business system, they account for more than 90% of the total daily business volume)

* The criticality is very high (the product manager believes that there must be no problems, such as login, etc.)

* Resource occupancy is very serious (resulting in very large disk I/O, for example, a business needs to access data from dozens of tables when submitting results, or a large number of data records will be retrieved when a query submits a request)

Description of performance requirements

Accurate For
example, the ** system must process 20 login tasks within a response time of no more than 10 seconds. Another example is that the maximum email sending time is no more than 5 seconds and the average time is less than 2 seconds.

Consistent
Users and performance test engineers must have the same understanding of related terms, such as the number of concurrent users, online users, and registered users:


The requirements for specific performance tests must be conditional.

Check whether the business operations meet the performance requirements during 12 hours of continuous operation under the load of 1500 users and 500 concurrent users running under the load of 10G of key business data in the background of the system and 20K of operating data.

General performance requirement description

1. The opening speed of the web homepage is less than 5s, and the web login speed is less than 15s.

2. Mail service supports 500,000 online users

3. The success rate of billing bills is over 99.999%.

4. In the peak period of 100 concurrent users, the basic functions of the mailbox, the processing capacity of at least 10QPS (TPS). QPS (TPS)-the number of requests/transactions per second

5. The system can operate stably for 12 hours when the operating pressure is 1 times higher than the actual system.

6. Can this system support 2 million VUs (the number of people who log in to the system every day) VU-Virtual user (virtual user)

Guess you like

Origin blog.csdn.net/Python_BT/article/details/108750998