...
Ramp-up Period (secs) | Number of Threads (Users) | Elapsed time of current running test | Response on UI | Loop Count |
|---|---|---|---|---|
1 | 20 | 2 sec | Callers are visible | 1 |
1 | 50 | 3 sec | Callers are visible in caller list | 1 |
1 | 1 | 7 sec | Callers are visible in caller list | 50 |
1 | 100 | 8 sec | Callers are not visible in caller list during load test | 1 |
1 | 1 | 13 sec | Callers are visible in caller list | 100 |
1 | 200 | 16 sec | Callers are not visible in caller list during load test | 1 |
1 | 1 | 26 sec | Callers are visible in caller list | 200 |
1 | 300 | 29 sec | Callers are not visible in caller list during load test | 1 |
1 | 500 | 50 sec | Callers are not visible in caller list during load test | 1 |
1 | 1 | 1 min 9 sec | Callers are visible in caller list | 500 |
5 | 500 | 47 sec | Callers are not visible in caller list during load test | 1 |
60 | 500 | 1 min 12 sec | Callers are visible in caller list during load test with delay of 5 to 6 secs | 1 |
100 | 500 | 1 min 39 sec | callers are not visible during load test | 1 |
1 | 1000 | 1 min 35 sec | Callers are not visible in caller list during load test | 1 |
1 | 2000 | 02 min 39 sec | Callers are not visible in caller list during load test | 1 |
1 | 100k | 1hour 52 mins | Callers and caller list are not visible after the load test. Container of caller list goes into unhealthy state. | 1 |
Note: this result Elapsed time of current running test can varies depending on configuration in jmeter, network latency, server performance/load.
Load Test Result for Easy Announcement and Business Calendar:
Thread Group 3:
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 | |
...