Versions Compared

Version Old Version 19 New Version 20
Changes made by

QA Team

QA Team

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

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 secssec

(5-6 min)

300k

200k (latest)

138 secs

(2-3 min)

200k

178k (latest)

60 secssec

(1min)

99999

78846

Note: there is some delay after uploading the csv on UI, time it took for callers visibility in caller list is around 5 to 8 mins.

...

Throughput in sample per unit: 70 ( 70 sample per min ~ The Timer element helps maintain a consistent total throughput value, but system issues or bottlenecks can still cause actual throughput to fall below the target value.)

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

  2. Ramp-up period:

...

  1. Each user will be started within 1 second of the test start.

  2. Loop count:

...

  1. Each user will execute the test plan 100,000 times.

  2. Thread

...

  1. lifetime: The test will run for 86,400 seconds (24

...

  1. hours).

  2. Throughput: The target throughput is 70 requests per second on average.

It means the 100k requests will be hit in duration of 24 hrs.

...

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

  • Thread Groups: Four, 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.

...

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

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

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)

100k70

1

1

60409

0.05 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

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

100k1

1

60393

0.055

sec

187 sec

0.7

sec

2.74 %

Fail

This table summarize the test result for Easy Announcement

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)

100k70

1

1

100k

0.027

sec

5.9

sec

0.05

sec

0.00 %

Pass

This table summarize the test result for Business calendar

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)

100k70

1

1

100k

0.033 sec

25 sec

0.06 sec

0.002 %

...