Performance test, load test, stress test What's the difference _ Performance test

Performance testing, load testing, stress testing What's the difference? Performance testing (or antisymmetric user concurrency performance testing), load testing, strength testing, and capacity testing are some of the areas of performance testing, but concepts can easily be confused. Here are a few concepts to introduce.

Performance test (performance Test): typically collects all the performance related to the test and is usually used by different people on different occasions.
Attention points: How much and how fast

Load test: Load test is a performance test that indicates whether the data is running in an overloaded environment and the program is able to afford it.
The point of concern: how much

Strength test (Stress test): Strength test is a performance test, he is in the system resources particularly low situation of software system operation, the purpose is to find out where the system and how the failure of the place. Including
Spike testing: A short time extreme load test
Extreme testing: Load test under excessive user
Hammer testing: Perform all actions that can be performed continuously

Capacity test (Volume test): Determine the maximum number of users that the system can handle simultaneously online
Focus: How much (not how fast)
Capacity testing, usually related to databases, differs in capacity and load in that capacity focuses on large capacity without the need to perform actual use.

Among them, capacity test, load test, strength test in English is explained:
Volume testing = Large amounts of data
Load testing = Large amount of users
Stress testing = Too Many users, Too much of data, Too little time and Too little


Maybe everyone's role performance testing, load testing, and strength testing are confusing. Yes, these three concepts are relatively easy to make people confused. Load tests and strength tests are subsets of the performance test. Here's a running example to explain.
A performance test that represents the best scenario that can be performed under a given benchmark. For example, it takes a lot of time to run 100 meters without heavy load (here, no weight is the benchmark).
The load test is also a performance test, but he is under a different load. For just that example, if the expansion is: 50 kg, 100 kg ... And so on, how long it takes you to run 100 meters.
Strength test, is in the strength of the performance test. For that example, if you were to: in the case of a strong wind, how much time would it take you to run 100 meters in the case of heavy or no weight.

Performance testing is power, load test loads, stress test strength

The pressure test stresstest is the effect of long time continuous running system to the system performance under certain load conditions.

Load Test LoadTest: Under a certain workload, the system caused by the load and system response time.

Stress testing is primarily to detect changes in the performance of software systems under one (arbitrary) set of conditions, by changing the input of the application to exert increasing load on the application (concurrent, cyclic, multi-user) and measuring performance changes in these different inputs, It is often said that the stress test investigates the maximum load that the system can withstand under the current hardware and software environment and helps to identify the bottleneck of the system. This test can also be called a load test, but a load test typically describes a specific type of stress test--increasing the number of users to stress test the application. For example, in practice, we say that starting from a relatively small load, we gradually increase the number of simulated users until the application response time times out, that is, the load test.

The objective of the stress test is to test the stability of the system for a long period of time under certain loads, pay particular attention to changes in the performance of long-running systems in large business situations (for example, whether the reaction slows down, whether a memory leak causes the system to collapse, and whether it can recover); Stress testing is a measure of system limitations and failure resilience, It consists of two kinds of situations:
Stability pressure test: Under the selected pressure value, long time continuous operation. Through this kind of pressure test, we can investigate whether the performance index is within the specified range, there is no memory leakage, there is no functional failure, etc.
Destructive stress tests: there may be some problems in the stability stress test, such as a significant reduction in system performance, but it is difficult to reveal the true cause. Through the destructive pressure of the means, often can quickly cause the collapse of the system or let the problem clearly exposed;

The goal of the load test is to test the performance of the system under a certain load (not focusing on the stability, that is, not focusing on the operation for a long time, but getting the relevant performance indicators under different loads); In practice, we often start with a relatively small load and gradually increase the number of simulated users Observe the application response time, the resources consumed under different loads, until the timeout or the critical resource is depleted, which is the load test, which is the performance indicator of the test system under different load conditions.

——————————————————————————————

In the simplest terms:

Load testing is the best performance test that the software can withstand.

Stress testing is a destructive performance test;

As long as you understand these two differences, it is very good to understand the performance test

From:http://zlfoxy.blogbus.com/logs/8040990.html

Http://blog.sciencenet.cn/blog-54317-563055.html