Page Comparison

...

2 CPU
4GB RAM
100GB Disk size

Uploading CSV Files (Diff callers volume) in Caller List (Performance Testing):

Limitation: During uploading the CSV file user is not able to view the callers in caller list.

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(Callers in all caller list not visible during that time and the same amount a db query took to show all callers)
300k	8-9 mins	300k	0	300k		7-8 mins (Callers in all caller list not visible during that time and the same amount a db query took to show all callers)
200k	3 mins	200k	0	200k	8064kb	ptcl sample data
200k	1 min	99999	100001	99999	5913kb	ptcl sample data
178845	57 sec	99999	78846		5407kb	ptcl sample data
100k	53	98784	1216		4677kb	ptcl sample data
100k	3 mins	100k	0	100k	3994kb
25k	34 sec	25k		25k		64 secs
25k	34 sec	25k
50k	24 sec	50k	0	50k

API

Load Test:

Software for load test: Apache JMeter

Why is it needed?

User need to know about the load testing of Supervisor tool. User have a call volume of over 100k on some helpline in PTCL and User will call supervisor tool caller list before those helplines. User need to know many hits can supervisor tool handle easily?
User can use a single caller list for all the helplines or separate for each helpline?

...

How many data user can add into a callerlist with affecting the response?

API for Load test

API load testing is done for caller list, Easy Announcement, Business Calendar

API for Easy announcement is used to get announcement(s) of type “General”. This gives the details of an easy announcement, including id, name and prompts string within the easy announcement.
API for caller list to check whether a specific caller exist in the list or not. It also returns the prompts associated to a particular caller list

HTTP Method	GET
URI	https://<adminpanel-server>:<port>/clm/callerInList/getCallerInLists?callingNumber={?}
Content Type	Application/JSON
HTTP Success Code	200
HTTP Failure Code	404,405

The Service Status API for Business calendar checks the status of a calendar, i.e. if the agency is Opened, Closed, has a Holiday or an Exceptional opening or closing. For more detail visit

Load test result is given with the following configuration:

Throughput in sample per unit: 70

Number of threads (users): 1

Ramp up period : 1 sec

Loop count: 100k

Thread Lifetime: 86400 secs (24 hr)

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

Following are the load test result Note: different elapsed time noted for different calling number in APi as can viewed in below ss of result view table as well.of thread(users)

Ramp-up Period (secs)

Number of Threads (Users)

Elapsed time of current running test

Ramp-up Period (secs)	Number of Threads (Users)	Elapsed time of current running test		Loop Count
1	20	2 sec	Callers are visible	1
1	50	6 sec	Callers are not visible in caller list during load testdifferent elapsed time noted for different number in APi as can viewed in below ss	1
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
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 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

Ramp-up time setting used to control how quickly virtual users are added to the test
Thread users indicates the number of virtual users running concurrently
Elapsed time of current running test is the total time the test has been running

20 mins (1200)

100k

Loop Count

1

hr 19 mins

Callers and caller list are not visible after the load test. Container of caller list goes into unhealthy state. after the load container is in healthy state and callers are visible in caller list later it went into again in unhealthy state, container status behavior is inconsistent

1

26 mins(1600sec)

100K

5 hour 55mins

Callers and caller list are not visible after the load test. Visible after 20 mins

1

24 hours (86400)

100k

1

100k

1