Various software requires some special requirements for customers in the system implementation. If the software system has not been tested and optimized, the software system will not meet the needs of users and will bring great risks to software in practical applications. Some companies lack the necessary test methods and tool knowledge lead to not complete, in which performance testing is an important aspect of the entire software test, how to do performance testing, how to perform performance testing is one of the regular discussions between testers and forums topic.
purpose:
Why do you perform performance testing?
The purpose is to verify that the software system can meet the performance indicators proposed by the user, and the performance bottleneck, optimization software exists in the software system, and finally the purpose of optimizing the system.
Including the following aspects
One. The ability to assess the system, the load and response time data obtained in the test can be used to verify the capabilities of the planned model and help make decisions.
two. Weakness in the identification system: controlled loads can be added to an extreme level, and break through it, thereby repairing the bottleneck or weak place of the system.
three. System Tuning: Repeated running tests, verifying the activities of the adjustment system have been expected, thereby improving performance. Problems in the detection software: Long-term test execution can result in the failure caused by memory leaks, revealing implicit problems or conflicts in the program.
four. Verification Stability (Reliability): Perform testing at a production load is the only way to assess whether system stability and reliability meet the requirements.
definition:
Performance test types include load testing, intensity testing, capacity testing, etc.
Load Test: Load Test is a performance test index operation in a super-load environment, whether the program can bear.
Strength Test: Intensity Test is a performance test, and he runs at a software system in the case of particularly low system resources.
Capacity test: Determine the maximum number of users that can handle simultaneous online
Observation indicator:
Performance testing is primarily tested by automated test tools to simulate a variety of normal, peaks, and abnormal load conditions to test the performance indicators of the system. Load testing and pressure tests belong to performance testing, both of which can be carried out. By load testing, it is determined that the performance of the system under various workloads is that the changes in the performance indicators of the system when the load is gradually increased. The pressure test is a test of the maximum service level of the system by determining the bottleneck or the performance point of a system or the performance point that cannot be received.
In practice, we often test two types of software: BS and CS, which are all contents of these performance indicators generally?
The general index generally focused on the BS structure program is as follows:
Web server indicator indicator:
* AVG RPS: Average average response per second = total request time / second;
* AVG TIME TO LAST BYTE PER TERSTION: The average number of iterations of the business corner per second, some people will confuse the two;
* Successful rounds: successful request;
* Failed rounds: failed request;
* Successful Hits: Successful click;
* Failed Hits: Clicked Clicks;
* Hits Per Second: Click on the number per second;
* Successful Hits Per Second: Clicked Clicks per second;
* Failed Hits Per Second: The number of clicks that failed per second; * Attempted connections: Try the number of links;
CS structural program, because the general software background is usually a database, so we pay more attention to the database's test indicators:
* User 0 Connections: User connection number, that is, the number of connections for the database;
* Number of deadlocks: Database dead lock;
* Butter Cache Hit: Database Cache's hit
Of course, in practice we will also look at the memory, CPU, system resource calls in multi-user testing. These indicators are actually a kind of performance test: competition test. What is a competitive test, software competition uses various resources (data records, memory, etc.) to see his ability to compete with other relevant systems.
