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

Measure performance impact on Kubernetes control plane #32

Open
2 tasks
voltbit opened this issue Nov 24, 2020 · 0 comments
Open
2 tasks

Measure performance impact on Kubernetes control plane #32

voltbit opened this issue Nov 24, 2020 · 0 comments
Labels
testing Code coverage and QA

Comments

@voltbit
Copy link
Contributor

voltbit commented Nov 24, 2020

Before the operator is production ready we need to measure the load put on the Kubernetes master and etcd by the operator and optimise the API calls if needed. We should be able to observe performance regresson for new features of code changes.
Possible requirements:

  • benchmark tests on the number of K8s API calls
  • benchmark tests on network load/traffic for K8s API calls + redis-cli calls

In particular any K8s API call done in a waiting poll should be considered an optimisation opportunity.

@voltbit voltbit added this to the Beta milestone Nov 28, 2020
@voltbit voltbit changed the title Measure performance impact on Kubernetes controll plane Measure performance impact on Kubernetes control plane Nov 28, 2020
@voltbit voltbit added the testing Code coverage and QA label Jan 17, 2021
@voltbit voltbit removed this from the Beta milestone Jan 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Code coverage and QA
Development

No branches or pull requests

1 participant