The classification of performance test scenarios, or the performance test we need to take into account those scenarios

1, the general performance test:

When we perform performance testing, the system is low-concurrency or no concurrency, and the system does not stress the test as a general performance test. The main factor is to verify that our system meets the performance requirements under normal circumstances. For example, two login system, if the system logon time is 8 seconds, then this system will not need to perform performance testing, because it does not even the general requirements

2. Load test:

Simulation users use real scenes, where the real scene is the need for data statistics, such as a novel website, we track the user's use of a year, found that the average 1000 people a day 80% people are uploading novels, 20% of people are constantly searching for novels, then we test will be based on this statistical data to test.

In real-world scenarios, we continue to increase the number of users proportionally, until the system performance inflection point, at this time long-running, to observe the systems are normal

What is the inflection point:

Here we take figure 6-239 as the inflection point analysis chart. The "Inflection point analysis" method is a method of performance analysis using the inflection points on the performance counter graph. Its basic idea is the performance bottleneck is the main reason is because of the use of a resource to reach the limit, at this time, with the increase in pressure, the performance of the system has declined sharply, thus creating a "inflection point" phenomenon. When the use of resources near "inflection point" is obtained, the performance bottleneck of the system can be located. Example of "Inflection point analysis" method, such as the system with the increase of users, transaction response time slowly increased, when the number of users reached 100 virtual users, the system response time increased sharply, as a clear "polyline", which shows that the system can not carry so many users to do this transaction, that is, there is a performance bottleneck.

3. Pressure test

In fact, in the case of system load operation, continue to increase the pressure to see if the software has a memory leak, core dump and other issues

4, the large data volume test:

Big data volume testing is mainly for the database has special requirements of the system testing, mainly divided into three kinds:
1. Real-time Big data volume: simulates the real-time large amount of data when the user is working, the main purpose is to test the user more or some business to produce a large amount of data, the system can run stably.
2. Limit state test: The test system is mainly used for a period of time when the system accumulates a certain amount of data, whether the normal operation of the business
3. The first two kinds of combination: The test system has accumulated a large amount of data, some real-time production of large data volume of the module can be stable to work.

5. Stability Test:

According to the work experience, the stability test is mainly the system to meet the requirements of performance indicators, for a long time operation, generally for the hour, observing whether the system has been working properly

6. Configuration test:

The test of configuration testing is to find out the optimal allocation principle of various resources of the system under different hardware and software configuration environment.

The classification of performance test scenarios, or the performance test we need to take into account those scenarios