...
Note: there is some delay after uploading the csv on UI, time it took for callers visibility in caller list is around 5 to 8 mins.
...
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
GET 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.
GET 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 GET API for 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
...
Total callers in db 463948
First load test was run for 24 hours for 100k (threads) each for easy announcement and business calendar. Both thread groups running concurrently and detailed load test results is in attached file.
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
| View file | ||
|---|---|---|
|
After that another load test Load test started for 24 hours for 100k (threads) each for All caller list and caller list easy announcement and business calendar concurrently and detailed load test results can be view in attached file.
...
Given is the resulted reports for all caller list, easy announcement and business calendar.
This summarize the test result for All caller List total callers 463948 in All callers.
Sr.no | API | Duration | Threads (users) | Ramp up (sec) | Number of sample( total http request hits) | Response Time(sec) GET API | Benchmark | Result | ||
|---|---|---|---|---|---|---|---|---|---|---|
Min | Max | Avg | Response time for GET API should not be more than 10 sec | |||||||
GET API | 24 hr (86400 sec) | 100k | 1 | 60409 | 0.05 sec | 187 sec | 0.7 sec | 2.74 % | Fail | |
This summarize the test result for a caller List having 100k caller in caller list
Sr.no | API | Duration | Threads (users) | Ramp up (sec) | Number of sample( total http request hits) | Response Time(sec) GET API | Benchmark | Result | ||
|---|---|---|---|---|---|---|---|---|---|---|
Min | Max | Avg | Response time for GET API should not be more than 10 sec | |||||||
GET API | 24 hr (86400 sec) | 100k | 1 | 60393 | 0.055 sec | 187 sec | 0.7 sec | 2.74 % | Fail | |
This summarize the test result for Easy Announcement
Sr.no | API | Duration | Threads (users) | Ramp up (sec) | Number of sample( total http request hits) | Response Time(sec) GET API | Benchmark | Result | ||
|---|---|---|---|---|---|---|---|---|---|---|
Min | Max | Avg | Response time for GET API should not be more than 10 sec | |||||||
GET API | 24 hr (86400) | 100k | 1 | 100k | 0.027 sec | 5.9 sec | 0.05 sec | 0.00 % | Pass | |
This summarize the test result for Business calendar
Sr.No | API | Duration | Threads (users) | Ramp up (sec) | Number of sample( total http request hits) | Response Time(sec) GET API | Benchmark | Result | ||
|---|---|---|---|---|---|---|---|---|---|---|
Min | Max | Avg | Response time for GET API should not be more than 10 sec | |||||||
GET API | 24 hr (86400 sec) | 100k | 1 | 100k | 0.033 sec | 25 sec | 0.06 sec | 0.002 % | ||
| View file | ||
|---|---|---|
|
...