Tested with UCCX 12-5 for ST 13.4.1
HW specs of the tested VM
2 CPU
4GB RAM
100GB Disk size
Uploading CSV Files (Diff callers volume) in Caller List (Performance Testing):
Limitation: During uploading the CSV file user is not able to view the callers in caller list.
Caller list | Upload time | Uploaded | Failed | Total in db | Delete through generic clear list (Time) |
|---|---|---|---|---|---|
200k | 2 mins | 200k | 0 | 200k | 4-5 mins (Callers in all caller list not visible during that time and the same amount a db query took to show all callers) |
300k | 8-9 mins | 300k | 0 | 300k | 7-8 mins (Callers in all caller list not visible during that time and the same amount a db query took to show all callers) |
API Load Test:
Software for load test: Apache JMeter
Why is it needed?
User need to know about the load testing of Supervisor tool. User have a call volume of over 100k on some helpline in PTCL and User will call supervisor tool caller list before those helplines. User need to know many hits can supervisor tool handle easily?
This is the api to check whether a specific caller exist in the list or not. It also returns the prompts associated to a particular caller list
HTTP Method | GET |
URI | https://<adminpanel-server>:<port>/clm/callerInList/getCallerInLists?callingNumber={?} |
Content Type | Application/JSON |
HTTP Success Code | 200 |
HTTP Failure Code | 404,405 |
Following are the load test result
Ramp-up Period (secs) | Number of Threads (Users) | Elapsed time of current running test | Loop Count | |
|---|---|---|---|---|
1 | 20 | 2 sec | 1 | |
1 | 50 | 6 sec | Callers are not visible in caller list during load test | 1 |
1 | 300 | 29 sec | Callers are not visible in caller list during load test | 1 |
1 | 500 | 50 sec | Callers are not visible in caller list during load test | 1 |
5 | 500 | 47 sec | Callers are not visible in caller list during load test | 1 |
60 | 500 | 1 min 12 sec | Callers are visible in caller list during load test with delay of 5 to 6 secs | 1 |
100 | 500 | 1 min 39 sec | callers are visible during load test | 1 |
1 | 1000 | 1 min 35 sec | Callers are not visible in caller list during load test | 1 |
1 | 2000 | 02 min 39 sec | Callers are not visible in caller list during load test | 1 |
1 | 100k | 1hour 52 mins | Callers and caller list are not visible after the load test. Container of caller list goes into unhealthy state. | 1 |
Ramp-up time setting used to control how quickly virtual users are added to the test
Thread users indicates the number of virtual users running concurrently
Elapsed time of current running test is the total time the test has been running
Ramp-up Period (secs) | Number of Threads (Users) | Elapsed time of current running test | Loop Count | |
|---|---|---|---|---|
20 mins | 100k | 1 hr 19 mins | Callers and caller list are not visible after the load test. Container of caller list goes into unhealthy state. after the load container is in healthy state and callers are visible in caller list later it went into again in unhealthy state, container status behavior is inconsistent | 1 |
26 mins | 100K | Callers and caller list are not visible after the load test. Visible after 20 mins | 1 | |
10 mins | 100k | 1 | ||
5 mins | 100k | 1 | ||
This is result for 100k threads and Ramp-up 20 mins, user faced issues for many threads in this load test “connection reset” error
