...
It means the 100k requests will be hit in duration of 24 hrs.
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 |
---|
name | summaryeasyannoucement.csv |
---|
|
View file |
---|
name | summarybusiness calendar.csv |
---|
|
After that another 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.
four thread groups were running concurrently.
Two scenarios were tested for all caller list a calling number is provided in API where it will checks in all caller list that the calling number exist or not in all caller list where total callers in caller list are 463948. While another scenario API includes only calling number and caller list and that caller list has 100k caller in it. so it checks either calling number exist in the caller list of 100k caller or not. These cases were tested to see the overall performance in both scenarios.
Given is the resulted reports for all caller list, easy announcement and business calendar.
View file |
---|
name | Invalid file id - 90c9f724-4e00-439d-98fb-345c4fe27242 |
---|
|
View file |
---|
name | Invalid file id - 5c6252ec-43f9-48d0-a296-bcc996a3dc6c |
---|
|
View file |
---|
name | Invalid file id - c413a925-b582-4950-87da-9047aea1b5c4 |
---|
|
View file |
---|
name | Invalid file id - 7961a2c6-d064-404c-a698-984b8caa8d4c |
---|
|
one thing noticeable is in caller API for 100k list the number in that calling list 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.
Image Added
Following are the load test result for different number of thread(users)
...