Execution strategy of application software efficiency test

　　 In order to meet the needs of different systems , According to the time and resource characteristics of the performance test , Several efficiency testing strategies for application software are formulated .

　　1. The benchmark

　　 Benchmark test refers to the test environment after confirmation , Benchmark each business involved in the business model , The purpose is to obtain various performance and resource usage indicators for single user execution , It provides reference for performance test and performance analysis of multi-user concurrent and mixed scenarios .

　　2. Concurrent test

　　 Concurrency testing refers to the concurrent execution of checkpoint operations by different numbers of virtual users , The purpose is to perform a pressure loading test on the checkpoint . Predict the system response time under certain user pressure after the system is put into use , Based on this response time analysis , Identify performance bottlenecks in the system , Provide basis for system optimization and adjustment .

　　3. Incremental test

　　 Incremental testing means that every certain period of time ( Such as 5 second 、10 second ) Concurrent checkpointing by different number of virtual users , Perform incremental user pressure loading tests on checkpoints , So as to simulate the real use scenario of the system , Enable users to predict the performance level of the system after it is put into use .

　　

　　4. Scenario test

　　 According to the statistical results of historical data and the distribution and use frequency of system users , Simulate different users to perform different operations , Such as 10% User performing login operation for ,50% Of users to perform query operations ,40% The user of performs database update operation , Simulate the real scene of the system to the greatest extent , Enable users to predict the real performance level of the system after it is put into use . So as to optimize and adjust the system accordingly , Avoid the system not responding and crashing for a long time in the actual situation .

　　5. Limit test

　　 Limit test refers to the performance limit test of the core function points of the system and the function points that may have pressure bottlenecks , That is, the maximum number of concurrent users that the function node can tolerate . Pass the limit test , Users can predict that after the system is put into use , Whether it can meet the actual needs .

　　6. Fatigue strength test ( Stability test )

　　 This test refers to the fatigue strength test for the core function points of the system , That is, the maximum number of concurrent users that the system can support under stable operation , Continuous execution of business for a period of time ( Such as 48 Hours ), Record transaction average response time , Transaction accuracy , Application server and database server CPU utilization 、 Memory usage and other parameters , Check whether the application server and database server are down 、 Memory leak, etc . This test usually needs to be combined with scenario testing , Thus, it can simulate the real environment to the greatest extent , Under the condition of long-term continuous operation of the system , Whether the system can be maintained in a stable operating state .

　　7. Data storage capacity test

　　 Use tools to continuously perform various tasks , Make the database store a certain capacity , Under different data storage capacity , Repeat the operation , Find the system response time . Compare different data storage capacities , System response time to perform different task operations , Enable users to predict the changes of data storage capacity in the future , Changes in response time for different task operations .

　　8. Memory leak detection

　　 Use the tool to simulate the use of the test point of the system in single user, multi-user concurrency and long-time running , Record the memory allocation and resource call of the system , So as to judge whether there is memory leakage at the test point of the system when single user and multi-user are concurrent .

　　 For more information on testing techniques, please pay attention to ： Shenzhen duosurveyor software and Technical Service Co., Ltd a