Shulou(Shulou.com)06/03 Report--

1. Benchmark test

When there is no pressure in the system, a single user iterates for a continuous time or number of times to obtain the average corresponding time of things as the standard of analysis and measurement.

The purpose is to measure whether the performance test environment is abnormal or not.

-> verify the correctness of scripts and parameters

-> get the performance data of the system processing things

two。 Concurrent testing

In the case of multi-concurrency of the system, the utilization of server hardware resources, network usage, application server and so on.

At the same time, you can also check whether the system server is robust (whether something logically correct will occur, and a logic error will occur in the case of juxtaposition. )

3. Mixed test

Mixed scenario testing, for typical scripts according to a certain proportion of mixed scripts (closest to the production environment), to find out the possible bottlenecks of the system

4. Surge test

Cross pressure tests of high intensity and low load to verify the stability of the system in both cases, in order to find out the problems caused by sudden occupation and release of system resources in the process of increasing and reducing load.

5. Capacity test

Measure the maximum capacity of the system. By constantly adjusting the load, we can find out the optimal capacity of the system under the condition of meeting the performance index, and the maximum number of concurrency of the system under this configuration.

6. Stability test

Simulate a certain number of users running for a long time to verify whether the success rate of user access to the system is reduced after running for a long time, in order to find out the potential memory leakage and other problems of the system.

7. Fatigue test

Is to test the saturated system. The maximum number of users under the condition of meeting the performance index is used to execute the service continuously for a period of time, and the performance index of the maximum workload processed by the system is determined by comprehensively analyzing the service execution index and resource monitoring index.

8. Extension testing

On the premise of knowing the performance bottleneck, increase the system capacity, or upgrade the hardware, and find out the performance bottleneck.

9. Batch testing

Processing large amounts of data, testing program processing efficiency (receiving data from upstream systems and transferring data to downstream systems within a specified period of time) and server resources

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.