软件测试中有关性能测试结果的几点分析原则（Analysis principles of performance test results in software testing）.docVIP

软件测试中有关性能测试结果的几点分析原则（Analysis principles of performance test results in software testing） Analysis principles of performance test results: Specific issues specific analysis (this is due to different application systems, different test purposes, different performance concerns) Find the bottleneck in the following order, from easy to difficult. The server hardware bottleneck - network bottleneck (on the LAN, can not consider) - server operating system bottleneck (parameter configuration) - bottleneck (parameter configuration, database middleware, web server (SQL) - application bottleneck statements, database design, business logic algorithm, etc.) Note: the above procedure is not required in each analysis, and the depth of analysis should be determined according to the purpose and requirement of the test. For some low requirements, we analyze the application system in the future large load pressure (concurrent user number, data volume), where the hardware bottleneck of the system is enough. In the analysis of performance test results, the subsection elimination method is very effective Sources of information for analysis: 1) according to the error information in the process of scene operation 2) monitoring index data collected according to the test results Error analysis of performance test results Analysis example: 1) Error: Failed to connect to server : [10060] Connection Error: timed out Error: Server has shut down the connection prematurely Analysis： A, application service dead. Small users: Problems on the program. The problem of processing database on program B, application services are not dead (application service parameter setting problem) Example: in many client connections, the Weblogic application server is rejected, and there is no error display on the server side, it may be that the AcceptBacklog attribute value of the server element in the Weblogic is set too low. If the connection refused message is received during the connection, the value should be