foreword
When I was doing a project for a client before, because I didn’t have a deep understanding of performance testing, and I didn’t understand the difference between stress testing and load testing, it was still handled by the colleague in charge of performance testing. He told me a lot about stress testing The difference between load testing and load testing is now summarized as follows.
pressure test
The purpose of the stress test is to evaluate the stability of the system and determine the performance of the system in extreme situations, such as: the maximum load the system can withstand, the stability under the extreme conditions of the system, and the reliability of the system. The purpose of stress testing is to find and fix problems when the system fails, and to provide fault tolerance and reliability guarantee for the system.
load test
The purpose of load testing is to evaluate the performance of the system under normal workload, such as: system response time, throughput, system resource utilization, etc. The purpose of load testing is to prove whether the system can meet the service requirements of users under normal load.
Of course, the above is only a basic explanation, and the following is a complete summary, hoping to help everyone.
The concept and difference of various performance tests
| test type | pressure test | load test | Benchmarks | configuration test | stability test |
|---|---|---|---|---|---|
| concept | Under the specified larger load, test the resilience of the system, as well as the ability to detect, respond and recover | Under a certain load that does not exceed the limit, the response ability of the system | Verify the correctness of the environment, the correctness of the script, and get the performance benchmark of the system | Test with different configurations | Control the load roughly at 50% or 70%, and check whether the system can run stably |
| Test Methods | Make requests to the system with a load of one or more times the system capacity | In the case of not exceeding the system capacity (double capacity), select multiple load points and request the system | Execute scripts in a single-scenario, single-user mode, and maintain consistency between multiple versions | Use different configurations, such as the number of threads, the number of database connections, JVM memory and other configuration classes for comparative testing | make requests to the system with the specified load |
| Observation point | Check the resilience of the system under multiple loads, such as the control of traffic, the recovery of components such as processes, and the ability to successfully process business volumes to double the capacity | System TPS, RT, resources (CPU, memory network, disk) | TPS, RT, system resource usage | System response under different configurations, such as TPS, RT | CPU fluctuation does not exceed 5%, memory fluctuation does not exceed 5% |
| Purpose | Monitor system deliverability and resilience in extreme environments | It is used to observe the overall situation of the system's ability changing with the business volume in the normal scene of the system, and is used to draw a graph; find out performance problems and risks, quantify the system capacity, analyze performance trends, and provide a basis for performance tuning | Performance comparison between different versions | Select the optimal configuration for performance tuning | Confirm that the system is stable and used for release confirmation |
| Common scene | Before release, delivery scene | system tuning | Preliminary understanding and comparison of performance | performance tuning | Before release, delivery scene |
Hope the above can help you.
Finally, I would like to thank everyone who has read my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, you can take it away if you need it:
These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey, and I hope it can help you! Partners can click the small card below to receive