1. Performance test classification:
1. Benchmark test
2. Concurrency testing
3. Load test
4. Stress test
1. Benchmark test:
- It is also a single-user test. After the test environment is determined, the important business in the business model is tested separately to obtain various performance indicators during single-user operation, which provides a reference for performance analysis such as multi-user concurrent testing and comprehensive scenario testing.
jmeter performance test video tutorial: 2023 latest detailed explanation of the whole process of the jmeter performance test project of a large factory, quietly collected, you will not see it later_哔哩哔哩_bilibili 
https://www.bilibili.com/video/BV1Vu411L77o/? spm_id_from=333.999.0.0
2. Concurrency testing
- It mainly refers to whether there are hidden concurrency issues when testing multiple users concurrently accessing the same application, module, and data, such as memory leaks, thread locks, and resource contention issues. Almost all performance tests involve concurrency testing.
- Multi-users perform an operation to form instantaneous pressure (accurate to milliseconds). It is a strict test that mainly examines the system's ability to withstand large instantaneous pressures.
jmeter performance test video tutorial: 2023 latest detailed explanation of the whole process of the jmeter performance test project of a large factory, quietly collected, you will not see it later_哔哩哔哩_bilibili https://www.bilibili.com/video/BV1Vu411L77o/? spm_id_from=333.999.0.0
3. Load test
- Load testing is a system load that simulates the load conditions borne by the actual software system. Through continuous loading (such as gradually increasing the number of simulated users) or other loading methods to observe the system response time, data throughput, and resources occupied by the system under different loads (such as CPU, memory), etc., to test the behavior and characteristics of the system to discover possible performance bottlenecks, memory leaks, and real-time synchronization problems in the system.
- Pressurize the system a little bit to find where the limit of the system is
4. Stress test
- Also known as strength test: it is a test under strong load (large data volume, a large number of concurrent users, etc.), to check the operating behavior of the application system under peak usage conditions, so as to effectively discover a certain functional hidden danger of the system and whether the system has good performance. fault tolerance and recoverability.
- Stress tests are divided into long-term (such as more than 24 hours) stability stress tests under high load and destructive stress tests that cause system crashes under extreme load conditions.
- Keep repeating the limit pressure of the system for a long time to see if the system can bear it
During the stress test, the system memory overflow solution:
Modify apache-jmeter-2.11\bin\jmeter.bat
