This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
High CPU usage on provider pods #248
Labels
bug
Something isn't working
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What happened?
We are running aws jet (v0.4.2) with 8 s3 resources and we saw that the provider pod is running at 800m which felt very wrong to us.
We upgraded to v0.5.0 and saw it drop to 600m which is better but still feels wrong.
For everyone else what is a reasonable load to expect or what have you seen run in the wild?
What metrics can we look at for potential problem points?
How can we reproduce it?
Run Jet-AWS provider from the Crossplane CRD resource.
Add 8 jet s3 resources.
Note CPU usage
What environment did it happen in?
Crossplane version: v0.4.2 and v0.5.0
Kube EKS v1.21
The text was updated successfully, but these errors were encountered: