Load Test Report

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):

Note: A delay of approximately 5 to 8 minutes occurs after uploading the CSV on the UI before callers become visible in the caller list.

Load Test:

Software for load test: Apache JMeter

API load testing is done for caller list, Easy Announcement, Business Calendar

GET API for Easy Announcement: Retrieves details of easy announcements, including ID, name, and prompts string.

GET API for Caller List: Checks if a specific caller exists in the list and returns associated prompts.

GET API for Service Status for Business Calendar: Determines the status of a calendar, indicating if the agency is Open, Closed, has a Holiday, or an Exceptional opening or closing. For more detail visit

Load test result is run with the following configuration:

1. Number of threads (users): 1 user will simulate the load.

2. Ramp-up period: Each user will be started within 1 second of the test start.

3. Loop count: Each user will execute the test plan 100,000 times.

4. Thread lifetime: The test will run for 86,400 seconds (24 hours).

5. Throughput: The target throughput is 70.

Total callers in db 463948

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 below.

• Thread Groups: Four, running concurrently

• Tested Scenarios:

  1. Checking if a provided calling number exists in a All caller list containing 463,948 callers.

  2. Verifying if a calling number exists in a caller list of 100,000 callers.

• Concurrency: Testing both scenarios concurrently (All caller list and caller list easy announcement and business calendar).

Detailed results are provided in the attached file for comprehensive analysis of the load test performance caller list, easy announcement and business calendar.

Thread Group 1:

This table summarize the test result for All caller List total callers 463948 in All callers.

Observations:

• The test successfully processed 60,409 HTTP requests within the specified duration (24 hr).

• The response time ranged from 0.05 seconds to 187 seconds, with an average response time of 0.7 seconds.

• A small percentage (2.74%) of requests experienced response times exceeding the threshold of 10 seconds.

Recommendation:

• Investigate and optimize the performance of the API to reduce the occurrences of response times exceeding 10 seconds.

Thread Group 2:

This table summarize the test result for a caller List having 100k caller in caller list

Observations:

• The test successfully processed 60,393 HTTP requests within the specified duration (24 hr).

• The response time ranged from 0.05 seconds to 187 seconds, with an average response time of 0.7 seconds.

• A small percentage (2.74%) of requests experienced response times exceeding the threshold of 10 seconds.

Recommendation:

• Investigate and optimize the performance of the API to reduce the occurrences of response times exceeding 10 seconds.

Thread Group 3:

This table summarize the test result for Easy Announcement

Observations:

• The test successfully processed 100k HTTP requests within the specified duration (24 hr).

• The response time ranged from 0.02 seconds to 5.9 seconds, with an average response time of 0.05 seconds.

• A percentage (0.00%) of requests experienced response times exceeding the threshold of 10 seconds.

Thread Group 4:

This table summarize the test result for Business calendar

Observations:

• The test successfully processed 100k HTTP requests within the specified duration (24 hr.)

• The response time ranged from 0.03 seconds to 25 seconds, with an average response time of 0.002 seconds.

• A percentage (0.00%) of requests experienced response times exceeding the threshold of 10 seconds.

one thing noticeable is in caller API for 100k list the number in that calling number expired due to TTL and the cron job started at 1 am so user can notice the http request failing after 1:00 as the number expired and removed after the TTL job as given below.

Different load test scenarios for caller list:

Scenario 1:

Load test result is run with the following configuration:

1. Number of threads (users): 1 user will simulate the load.

2. Ramp-up period: Each user will be started within 1 second of the test start.

3. Loop count: Each user will execute the test plan 4167 times.

4. Thread lifetime: 3600 (1 hour).

one thing noticeable thread 1 for caller list having 100k callers elapsed time 18 min:57 sec and for thread group all caller (4 min 30 sec diff). So, response time for All caller (874140 callers) where a caller list name is not mentioned to search a number from that list is more better than the caller with caller list name.

Total callers in db 874140

Thread Group 1:

This table summarize the test result for All caller (874140)

Thread Group 2:

This table summarize the test result for a caller List having 100k caller in caller list

Scenario 2:

Load test result is run with the following configuration:

1. Number of threads (users): 1 user will simulate the load.

2. Ramp-up period: Each user will be started within 1 second of the test start.

3. Loop count: Each user will execute the test plan 900 times.

4. Thread lifetime: 900 sec (15 mins)

total elapsed time: 4 min 17 sec

Total callers in db 874140

Thread Group 1:

This table summarize the test result for All caller List caller (874140 db)

Thread Group 2:

This table summarize the test result for a caller List having 100k caller in caller list

Following are the load test result for different number of thread(users)