First, the needs analysis
Performance testing mainly from the following two user side, to determine the performance testing requirements:
- First, business users
- Users frequently used, and there are a large number of business processes used by the user
- A higher proportion of transactions, accounting for more than 80% of daily even higher business processes
- Special trading day or peak trading accounted for more than 80% even higher business processes
- Poor performance and has been adjusted orchestration
- Special business scene
- Major core business processes to adjust business processes
- Second, the project team
- After adjustments have tested the performance of the architecture of business
- Complex logic, critical business
- You may consume a lot of resources of business
- Call interface with external systems exist, and there is a large amount of business data exchange
- Call third-party business components, complex business logic
Second, concurrent calculation
150,000 single-day volume of business, according to 28 principles for analysis, 80% of the traffic concentration within 20% of the time, a total of four hours one-day peak:
150 000 * 80% = 120 000
24 hours * 20% = 4.8 hours
4 hours /4.8 hr = 83%
4 hours the total inspection time, the magnitude of the desired traffic:
120 000 * 83% = 99600
2 hours of the test as a reference point, the desired amount of traffic:
120 000 * (2 /4.8 h h) = 50,000
Through the above analysis, the need to test the platform to support 50,000 users log in within two hours
Single user thread to run, calculating a reference time required for each segment of business, use of consumption of a single sample of 90%: 135 + 88 = 222 ms, plus the latency page operation, the total time required: 0.223s + 5s + 3s + 3s = 11.223s
The number of threads into the formula, simulate two hours to get the required 50,000 business users to:
total_Thread=50000/(2*60*60/11.223)=77.88
Rounding, the number of threads is 78