One: Load test-calculate the maximum concurrency
In the process of performance testing, we should first design test scenarios to simulate the real business situation, and then pin
Design test scripts for these scenarios. In order to expose performance problems, try to simulate as much as possible the possible existence of the tested object
In the bottleneck test scenario
Using a locally deployed project, we can use it to simulate attendance clocking business.
Business Process:
Check-in home page–click to log in–Jump item–open the attendance page–check-in attendance
Performance requirement index:
Business expectations The daily attendance is 400/min, which is 6.6/s
< div> Calculate the number of threads that need to be loaded:
Thread = BC/(60/t) = BC*(t/60)
t: Single user and single service consumption time , As far as possible to simulate the real behavior of the user
Single time consumption = open the homepage (0.5s) + thinking time (3s) + input username and password (1.5s) + homepage response time
< div> (0.5s) + attendance check-in time (3s)=8.5s (take 90% line)
BC: business volume, in this case BC=400
single business consumption 8.5s
One: Load test-calculate the maximum concurrency
In the process of performance testing, we should first design test scenarios. Simulate real business scenarios, and then design test scripts for these scenarios. In order to expose performance problems, try to simulate the possible existence of the tested object as much as possible.
Test scenarios in the bottleneck
Using a locally deployed project, we can simulate attendance clocking business.
Business Process:
Check-in home page–click to log in–Jump item–open the attendance page–check-in attendance
Performance requirement index:
Business expectations The daily attendance is 400/min, which is 6.6/s
< div> Calculate the number of threads that need to be loaded:
Thread = BC/(60/t) = BC*(t/60)
t: Single user and single service consumption time , As far as possible to simulate the real behavior of the user
Single time consumption = open the homepage (0.5s) + thinking time (3s) + input username and password (1.5s) + homepage response time
< div> (0.5s) + attendance check-in time (3s)=8.5s (take 90% line)