...
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.
...
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.
...
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.
...
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:
Number of threads (users): 1 user will simulate the load.
Ramp-up period: Each user will be started within 1 second of the test start.
Loop count: Each user will execute the test plan 4167 times.
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:
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 2 sec | |||||||
GET API | 3600 | 1 | 1 | 4167 | 0.171 sec | 2.98 sec | 0.20 sec | 0.02 % (1 request) | pass | |
This table summarize the test result for All caller (874140)
...
Thread Group 2:
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 2 sec | |||||||
GET API | 3600 | 1 | 1 | 4167 | 0.22 sec | 2.20 sec | 0.271 sec | 0.02 % (1 request) | pass | |
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:
Number of threads (users): 1 user will simulate the load.
Ramp-up period: Each user will be started within 1 second of the test start.
Loop count: Each user will execute the test plan 900 times.
Thread lifetime: 900 sec (15 mins)
total elapsed time: 4 min 17 sec
Total callers in db 874140
Thread Group 1:
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 2 sec | |||||||
GET API | 900 | 1 | 1 | 4167 | 0.17 sec | 0.66 sec | 0.20 sec | 0.00 % (0 request) | pass | |
This table summarize the test result for All caller List caller (874140 db)
...
Thread Group 2:
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 2 sec | |||||||
GET API | 900 | 1 | 1 | 900 | 0.22 sec | 4.8 sec | 0.271 sec | 0.22 % (2 request) | pass | |
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)
...