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
We are facing some high CPU usage from istio-sidecar:
DEV istio-poxy CPU usage comments-service:
INT istio-proxy CPU usage for comments-service:
So as you can see the istio-proxy sidecar in DEV is consuming a high CPU when compared with PROD and INT.
The environment configurations related to istio are the same. Tiring to solve the issue, we removed Istio telemetry and also logging, metrics tools like prometheus and Loki, and didn’t work.
The top command inside the service container in DEV:
comments-service-5f595f947c-tnhsr
We couldn't really figure out what is making istio to consume that amount of CPU yet. It's making our environment scale when should not.
Any help is welcome about how to possibly investigate it deeper.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are facing some high CPU usage from istio-sidecar:
DEV istio-poxy CPU usage comments-service:
INT istio-proxy CPU usage for comments-service:
So as you can see the istio-proxy sidecar in DEV is consuming a high CPU when compared with PROD and INT.
The environment configurations related to istio are the same. Tiring to solve the issue, we removed Istio telemetry and also logging, metrics tools like prometheus and Loki, and didn’t work.
The top command inside the service container in DEV:
comments-service-5f595f947c-tnhsr
We couldn't really figure out what is making istio to consume that amount of CPU yet. It's making our environment scale when should not.
Any help is welcome about how to possibly investigate it deeper.
Beta Was this translation helpful? Give feedback.
All reactions