Stress testing and load testing

Sometimes confusing two concepts together.
But to separate, then, it is so --------
(pcl To quote the words of)
the difference between the stress test (STRESSTEST) and load testing (LOADTEST) What? "
Let us first understand what is stress testing, load testing
stress testing under certain load conditions, continuous operation for a long time to affect system performance caused.
Load testing: under certain workloads caused by the system load and system response time.
distinguish them from the concept, it can be seen there is a long-running the stress test, the test load and the load type may be other types.
stress test is to find the software in a (any) given conditions changes in system performance. by changing the input is applied to the application to the application of increasing loads (concurrent, looping operation, multi-user) and measuring changes in the properties of these various inputs, it is often said to the concept: pressure test inspection system under maximum load current hardware and software environment can bear and to help identify system bottlenecks in fact, this test is also called a load test, but load testing is usually to describe a specific type of stress testing - increase the number of users to stress test the application.

For example, in practice we say from a relatively small load, gradually increase the number of simulated users until the application response time expires, that is to say the load test.


----
again quote the content of the web test

2, load testing

  Web load test is to measure a load on the system level performance, to ensure that the Web system to work properly within the range of needs. Load level may be at some point the number of users simultaneously accessing Web systems, can also be a number of online data processing. For example: Web applications can allow the number of simultaneous users online? If you exceed this number, What will happen? Web applications can handle a large number of user requests for the same page?

  3, stress test

  Load testing should be scheduled, tested in a real network environment after the Web publishing system. Because an enterprise internal staff, especially the project team is always limited, and the number of requests a Web system can simultaneously process will be far beyond this limit, therefore, only on the Internet, accept the load test, the result is correct credible.

  Stress testing is the actual destruction of a Web application reflects the system, the test system. Stress testing is to limit the ability to test and fault recovery system, that is, Web application testing system will not collapse, in what circumstances would collapse. Hackers often the wrong data load until the Web application system crash, then gain access when the system is restarted.

  Stress testing area includes forms, landing pages and other information transmission and so on.

The most simple terms:
load testing is to test the software itself can bear the greatest performance testing;
stress test is a destructive performance testing;
once you understand the difference between these two points, it is very easy to understand performance testing.


Zhou Feng understand:
these concepts should be said is chaotic. I understand:
1, the performance tests is a large category, including testing performance in various business scenarios, including response time, resource usage, system capacity limit like; load test, a pressure test

And capacity test sample from different angles to test only a performance test only;
2, the target pressure stability test is the test run for a long time under a certain load system, particular attention to long-running performance under heavy traffic situation change (e.g., whether the
slow reaction, if a memory leak will cause the system to gradually collapse, whether recovery); limiting stress testing and fault recovery capability testing system, which includes two cases:
stability stress test: in selected under pressure, long-lasting operation. Through such stress tests, can examine the performance indicators within the specified range, with or without memory leaks, with or without functional failure;
destructive stress tests: there may be some problems in the stability of the stress tests, such as system performance significantly reduced, but it is difficult to expose its true cause. By means of destructive constantly pressurized, often resulting in rapid collapse of the system or make obvious problems exposed;
3, the target load testing is to test the system performance under certain load (not concerned about stability, that does not concern the long run, but to obtain performance metrics related to different load)
; in practice, we often start from a relatively small loads, increasing numbers (increased load) simulated users observed under different load application response time, the consumption of resources , or until a timeout off
key resource exhaustion, which is a load of said test, which is the performance under different load testing system;
4, the test may determine the capacity of the overall system capacity to handle traffic, including different configurations, different the maximum number of users in a scene, the maximum number of records processed data, processing the maximum file size, the maximum transaction amount. It is the ultimate test of the capacity of the system.

 

Guess you like

Origin www.cnblogs.com/zzcsza/p/11980462.html