Answer: High concurrency Performance Test Plan for ten thousand students in the system: 2018.10.30

Performance testing objective: to locate the current server bottleneck through high concurrency stress testing.

Performance test scope: (analyze logs during peak business hours)

1. socket-related (Instructor-side network monitoring, whiteboards, Allocation Analysis cards, exercise cards, student-side network monitoring, and student questions)

2. HTTP interface (add multiple teaching points, obtain Classroom Information interfaces, custom evaluation, and intelligent exercise cards for preparing lessons on the instructor side)

Performance test plan:

1. Simulate and test the running status of system servers in 0.1 million online users.

2. Concurrency = online users/10

3. Use jmeter to send 1 million concurrent requests per second. Check whether the system has reached the bottleneck.

4. bottleneck judgment basis: 1. The server resource exceeds the performance test indicator. 2. the throughput starts to decrease. 3. The response time starts to rise.

Performance Test indicators:

1. The response time of all requests cannot exceed 3 seconds.

2. the CPU usage of the server cannot exceed 70%.

3. The memory size of the server cannot exceed 70%.

4. the disk I/O of the server resource cannot be full

5. The bandwidth usage of the tested server cannot exceed 70%

Performance test plan:

1. Test script preparation includes test account generation-August 1, November 6

2. Test server deployment-September November 6

3. Distributed Test server construction-November 13

4. test environment rehearsal-August 1, November 26

5. monitor various metrics and back up the database of the servers tested before the test. Notify the customer service system for maintenance-January 1, November 28.

6. Performance Test report section-November 1, November 30

7. Data cleaning after testing-January 1, November 29

8. Functional regression testing and verification system recovery-January 1, November 29

9. notify Customer Service that the system will be restored-January 1, November 29

Preparation for performance testing:

1. Create a testing organization-Answer performance test

2. Instructor-side test account and student-side test account

3. generate valid long tokens

Tested server architecture:

One websocket server, one front-end server, one MongoDB Cache Server, one redis Cache Server, one backend server, and one database server, other cloud services (CDN qiniu, audio and video network)

Test Server Configuration:

5 windows server2008 R2 system, CPU inter E5-2682 2.5 GHz, 8 GB memory

Performance testing tool:

1. Tool Selection jmeter

2. Install and deploy Java

3. Install and deploy jmeter. Note that jmeter must be installed at the first level of disk D.

4. Add the ext extension file to the Lib file to ensure that websocket can be used.

5. Global parameter token Configuration

6. Http head Configuration

7. Logical Controller-cyclic Controller

8. JSON Extract

9. distributed deployment

 

Performance test report:

　　

 

Answer: High concurrency Performance Test Plan for ten thousand students in the system: 2018.10.30