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

Determine Strategy for Performance Tests #10534

Open
sam-heilbron opened this issue Dec 24, 2024 · 0 comments
Open

Determine Strategy for Performance Tests #10534

sam-heilbron opened this issue Dec 24, 2024 · 0 comments

Comments

@sam-heilbron
Copy link

Do you have a suggestion for code improvement or tracking existing technical debt? Please describe.

There are a collection of performance tests which exist in the Gloo OSS project. They started to run on machines that ran out of space, and it raised the question of how we should define and run these.

In the short-term, we have disabled those tests for two reasons:

  • They are built using our Edge Gateway APIs, and do not support the K8s Gateway APIs
  • They have not been modified since they were introduced, and have not alerted us to performance issues

Describe the solution you'd like

No response

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant