Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Load testing #3832

Closed
zroubalik opened this issue Nov 9, 2022 · 3 comments
Closed

Load testing #3832

zroubalik opened this issue Nov 9, 2022 · 3 comments
Labels
help wanted Looking for support from community stale-bot-ignore All issues that should not be automatically closed by our stale bot testing

Comments

@zroubalik
Copy link
Member

Proposal

We should set up some load test, that will stress KEDA and run it regurarly to catch perf regressions.

Steps:

  1. Design the test case
  2. Implement the test
  3. Make it part of CI and set up to run periodically (nightly?)

Use-Case

No response

Anything else?

No response

@zroubalik zroubalik added needs-discussion feature-request All issues for new features that have not been committed to help wanted Looking for support from community testing stale-bot-ignore All issues that should not be automatically closed by our stale bot and removed needs-discussion feature-request All issues for new features that have not been committed to labels Nov 9, 2022
@tomkerkhove
Copy link
Member

What is the scope of perf testing, we should define that as well.

For example, we need to perf test metric server, but also our external scaler approach (mainly push)

@JorTurFer
Copy link
Member

Let me work on this as part of the testing proposal I'm working on to improve trust in KEDA and I'll link this there

@JorTurFer
Copy link
Member

This is duplicated: #4411

@tomkerkhove tomkerkhove closed this as not planned Won't fix, can't repro, duplicate, stale Jun 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Looking for support from community stale-bot-ignore All issues that should not be automatically closed by our stale bot testing
Projects
Archived in project
Development

No branches or pull requests

3 participants