You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
In particular any K8s API call done in a waiting poll should be considered an optimisation opportunity.
The text was updated successfully, but these errors were encountered: