(4.4.11) GC LoadTest Report

soad Test Cycle 1:

Hardware Specs:

CPU	RAM	Hard Disk
8 VCPU	16 GB	102 GB

#

Component

Scenario

Benchmark

Notes

Response Time (s)

Test Result

Comments

1

GC

Login 500 agents and Logout

CPU usage shouldn't be more than 70%

CPU Load:
- Max 64% (CPU Spike)
- Min 3-5%
RAM used:
- 2.64GB to 0.81GB/15.51GB

Min: 3.1s

Max: 31.3s

Avg: 11.2s

479 Passed out of 500

21 agents couldn't login/logout due to device failure

Login 500 agents and Make ready

CPU usage shouldn't be more than 70%

CPU Load:
- Max 66% (CPU Spike)
- Min 3-5%
RAM used:
- 2.64GB to 0.81GB/15.51GB

Min: 1.1s

Max: 6.1s

Avg: 3.59s

480 Passed out of 500

20 agents couldn't login/ready due to device failure

Put 500 Inbound calls on 500 agents

CPU usage shouldn't be more than 70%

CPU Load:
- Max 62% (CPU Spike)
- Min 3-5%
RAM used:
- 2.98GB to 0.89GB/15.51GB

Min: 9.8s

Max: 17.4s

Avg: 14.6s

489 Passed out of 500

11 agents couldn't login/ready due to device failure

Load Test Cycle 2:

#

Component

Scenario

Benchmark

Notes

Response Time (s)

Test Result

Comments

1

GC

Login 1000 agents and Logout

CPU usage shouldn't be more than 80%

CPU Load:
- Max 77% (CPU Spike)
- Min 7-11%
RAM used:
- 3.49GB to 0.81GB/15.51GB

Min: 6.1s

Max: 30.9s

Avg: 19.5s

947 Passed out of 1000

53 agents couldn't login/logout due to device failure

Login 1000 agents and Make ready

CPU usage shouldn't be more than 80%

CPU Load:
- Max 75% (CPU Spike)
- Min 7-11%
RAM used:
- 4.00GB to 0.86GB/15.51GB

Min: 2.4s

Max: 13.1s

Avg: 7.27s

926 Passed out of 1000

74 agents couldn't login/ready due to device failure

Put 1000 Inbound calls on 1000 agents

CPU usage shouldn't be more than 80%

CPU Load:
- Max 79% (CPU Spike)
- Avg 9-11%
RAM used:
- 4.03GB to 0.89GB/15.51GB

Min: 15s

Max: 36s

Avg: 21s

928 Passed out of 1000

72 agents couldn't login/ready due to device failure

GC has been tested with 1000 concurrent agents with 1000 concurrent calls and you can find the load test report detail here