Tested with UCCX 12-5 for ST 13.5
HW specs of the tested VM
2 CPU
4GB RAM
100GB Disk size
Uploading CSV Files (Diff callers volume) in Caller List (Performance Testing):
Caller list | Upload time | Uploaded | Failed | Total in db | File size | Delete through generic clear list (Time) |
|---|---|---|---|---|---|---|
200k | 2 mins | 200k | 0 | 200k | 4-5 mins | |
300k | 8-9 mins | 300k | 0 | 300k | 7-8 mins | |
200k | 3 mins | 200k | 0 | 200k | 8064kb | ptcl sample data |
200k | 1 min | 99999 | 100001 | 99999 | 5913kb | ptcl sample data |
178845 | 57 sec | 99999 | 78846 | 5407kb | ptcl sample data | |
100k | 53 | 98784 | 1216 | 4677kb | ptcl sample data | |
100k | 3 mins | 100k | 0 | 100k | 3994kb | |
25k | 34 sec | 25k | 25k | 64 secs | ||
25k | 34 sec | 25k | ||||
50k | 24 sec | 50k | 0 | 50k |
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?
User can use a single caller list for all the helplines or separate for each helpline? How many data user can add into a callerlist with affecting the response?
API for Load test
API load testing is done for caller list, Easy Announcement, Business Calendar
API for Easy announcement is used to get announcement(s) of type “General”. This gives the details of an easy announcement, including id, name and prompts string within the easy announcement.
API for caller list to check whether a specific caller exist in the list or not. It also returns the prompts associated to a particular caller list
The Service Status API for Business calendar checks the status of a calendar, i.e. if the agency is Opened, Closed, has a Holiday or an Exceptional opening or closing. For more detail visit
Load test result is given with the following configuration:
Throughput in sample per unit: 70
Number of threads (users): 1
Ramp up period : 1 sec
Loop count: 100k
Thread Lifetime: 86400 secs (24 hr)
It means the 100k requests will be hit in duration of 24 hrs.
Following are the load test result for different number of thread(users)
Ramp-up Period (secs) | Number of Threads (Users) | Elapsed time of current running test | Loop Count | |
|---|---|---|---|---|
1 | 20 | 2 sec | Callers are visible | 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 |
Later tested Again with different calling number Results are given
