...
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 | |
200k | 1 min | 99999 | 100001 | 99999 | 5913kb | |
178845 | 57 sec | 99999 | 78846 | 5407kb | ||
100k | 53 sec | 98784 | 1216 | 4677kb | ||
100k | 3 mins | 100k | 0 | 100k | 3994kb | |
25k | 34 sec | 25k | 25k | 64 secs | ||
25k | 34 sec | 25k | ||||
50k | 24 sec | 50k | 0 | 50k | ||
194817 | 27 lacs callers db | 182 secs (also a delay of callers visibility | ||||
594817 | 25 lacs callers db | 708 sec ( some delay in callers visibility in caller list) | ||||
300k (latest) | 324 sec (5-6 min) | 300k | ||||
200k (latest) | 138 secs (2-3 min) | 200k | ||||
178k (latest) | 60 sec (1min) | 99999 | 78846 | |||
178k | 178 sec | 99999 | 78846 | |||
178k | 89 sec | 178k | 5636kb | |||
300k (latest) | 239 sec | 300k | 13954kb | |||
178k | 79 sec | 2635877 | 5636 kb | |||
300k | 108 sec | |||||
650k | 249 sec ( 5-7 mins delay in visibility of callers in caller list) |
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.
...
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:
Sr.no | API | Duration | Constant Throughput Timer | 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) | 70 | 1 | 1 | 60409 | 0.05 sec | 187 sec | 0.7 sec | 2.74 % | Fail | |
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.
...
Investigate and optimize the performance of the API to reduce the occurrences of response times exceeding 10 seconds.
Consider scaling resources or optimizing code to handle peak loads more efficiently.
...
Thread Group 2:
Sr.no | API | Duration | Constant Throughput Timer | 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) | 70 | 1 | 1 | 60393 | 0.055 sec | 187 sec | 0.7 sec | 2.74 % | Fail | |
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.
...
Investigate and optimize the performance of the API to reduce the occurrences of response times exceeding 10 seconds.
Consider scaling resources or optimizing code to handle peak loads more efficiently.
...
Thread Group 3:
Sr.no | API | Duration | Constant Throughput Timer | 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) | 70 | 1 | 1 | 100k | 0.027 sec | 5.9 sec | 0.05 sec | 0.00 % | Pass | |
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:
Sr.No | API | Duration | Constant Throughput Timer | 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) | 70 | 1 | 1 | 100k | 0.033 sec | 25 sec | 0.06 sec | 0.002 % | pass | |
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.
...
Following are the load test result for different number of thread(users)
...