Skip to content
This repository has been archived by the owner on Feb 7, 2025. It is now read-only.

Load Test Performance fixes #821

Closed
1 task
jcrichlake opened this issue Jan 30, 2024 · 2 comments
Closed
1 task

Load Test Performance fixes #821

jcrichlake opened this issue Jan 30, 2024 · 2 comments
Labels
devex/opex A development excellence or operational excellence backlog item.

Comments

@jcrichlake
Copy link
Contributor

jcrichlake commented Jan 30, 2024

DevEx/OpEx

There are issues around our load tests, these include

  1. Our load test doesn't by default choose the non-local implementation
  2. We lack a way to monitor the internal application performance. This means we don't have a way to diagnose any problem areas that arise from failed load tests
  3. We may need to re-examine our load test assumptions, we are currently ramping up to 1k users and then hammering the various endpoints, this may be an amount of load that is either far off in the future or will require multiple instances of the intermediary running to handle it.

Tasks

  • Update ADR if needed
@jcrichlake jcrichlake added the devex/opex A development excellence or operational excellence backlog item. label Jan 30, 2024
@basiliskus
Copy link
Contributor

The test should probably choose the storage implementation depending on the ENV variable. If it's local, use the local implementation, otherwise use the DB one

@pluckyswan
Copy link
Contributor

We are closing this issue because another card covers it and is more of a priority . Any issues related to this card that are not covered can later be created again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
devex/opex A development excellence or operational excellence backlog item.
Projects
None yet
Development

No branches or pull requests

3 participants