Purpose of performance testing:
The purpose of performance testing is to verify whether the software system can achieve the performance indicators proposed by the user, and at the same time to discover the performance bottlenecks existing in the software system to optimize the software; including: assessing system capabilities, identifying weaknesses in the system, system tuning, and detecting existing software. problems, verify the stability and reliability;
Common classifications of performance testing:
Load testing, stress testing, capacity testing;
Common indicators of performance testing:
For the B/S framework, we generally focus on the following indicators:
Avg Pps: average number of responses per second = total number of requests/second;
Avg time to last byte per terstion(msters): The average number of iterations of business scripts per second;
Successful Rounds: successful request;
Failed Rounds: failed requests;
Successful Hits: the number of successful hits;
Failed Hits: The number of failed hits;
Hits Per Second: the number of hits per second;
Successful Hits Second: The number of successful hits per second;
Failed Hits Per Second: The number of failed hits per second;
Attempted Connections: number of attempted connections;
Throughput: Throughput rate.
For the C/S framework, since the software background is usually a database, we pay more attention to the test indicators of the database:
Uesr Connection: The number of user links, also known as the number of database links;
Number of Deadlocks: database deadlocks;
Butter Cache Hit: The hit situation of the database Cache.