[RP-IVR] Load Testing to increase number of users

[vivek-kumar-pandey]

Is your feature request related to a problem? Please describe. We want to check how the system will behave if we increase the user base. So we need to check and come up with the behavior seen in the system by increasing the users by an x number to check the pattern.

Describe the solution you'd like Need to implement a load testing tool and check the load that can be handled by the system successfully. For this, we can go with the following plan:

• [x] List down the details of the current load - 2 pointer
• [ ] Replicate the production infrastructure - Create a replica cloud function and database to isolate the testing from the production server - 3 pointers
  • [ ] All the components should be replicated and configured similar to what we have in production
  • [ ] We have to maintain a similar set of data in our database to simulate the production environment.
  • [ ] Test and validate the end-to-end application processing -
  • [ ] Make sure it doesn’t have any impact on the production environment in any way.
  • [ ] We use serverless VPC connector to connect applications with the database - need to make sure we use the same connection in replication
• [ ] Load testing - 5 pointers - We are going with [k6 load testing tool](https://k6.io/open-source/) as it is open source and we can write our cases to simulate the expected load
  • [ ] Setup up development env for K6
  • [ ] Write the test cases to simulate the behaviour
  • [ ] Run the test for the current load and check the behaviour
  • [ ] Ramp up the number of users 2x, 3x and up to 5x to get an idea of the current capacity and when to scale up the infrastructure.
  • [ ] Identify performance bottlenecks
• [ ] Create an analysis report, and action items for the future and share it across the team - 2 - 3 pointers
• [ ] Post-load testing cleanup - 1 pointer
  • [ ] List down the resources we created while replicating the infrastructure
  • [ ] Remove each resource from the replica infrastructure
  • [ ] Make sure every individual resource we created should be removed
• [ ] Documenting the load testing for future testing - 1 - pointer
  • [ ] This is from a process perspective, we should have things documented for future load testing reference.

Describe alternatives you've considered NA

Additional context

• this request came from Kriti to check the system's behaviour on increasing the number of users. We need to come up with the analysis that after increasing x users we need to scale our system

Acceptance Criteria

• [ ] Come up with a detailed analysis of the load testing

Documentation

• [ ] Document the process of load testing
• [ ] Document the analysis result

[Satendra-SR]

As the user impact is not even 0.5%, we are keeping it in the backlog for now - will pick this item as load increases in the future.