Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
pilot discovery cpu usage is too high #6962
Describe the bug
pilot-discovery cpu uasage is about 20% running bookinfo sample.
not too much cpu
Steps to reproduce the bug
run sample bookinfo
Is Istio Auth enabled or not?
referenced this issue
Aug 12, 2018
Did a bit of digging around and I think the idle CPU usage is due to
I'm not sure why the queue is implemented with a slice and sleeping as opposed to a channel, but the channel approach seems to work better at doing nothing :)
Yes, that's been a problem for a long time. We planned to get rid of it as we refactor the serviceregustry to event based ( there will be no queue), and for config galley would take over k8s integration, so lower priority.…
On Tue, Aug 21, 2018, 10:27 Darren Shepherd ***@***.***> wrote: Did a bit of digging around and I think the idle CPU usage is due to https://github.com/istio/istio/blob/adb21944b0a79fabe9c67eba55549b6308b7f1d1/pilot/pkg/serviceregistry/kube/queue.go#L108. The queue appears to run at the ratelimit all the time. So something like 10 times a second it wakes up and does nothing. I changed the implementation of queue.go to use a channel and my CPU usage went to 0.3% from a consistent 12% on my system. I'm not sure why the queue is implemented with a slice and sleeping as opposed to a channel, but the channel approach seems to work better at doing nothing :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6962 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFI6tbpB2GPw2c9WQHQQy_R83ITzDj7ks5uTEMbgaJpZM4VI4db> .
referenced this issue
Aug 22, 2018
I'm seeing the same thing:
Docker desktop for Mac is sitting at a continuous 30% CPU consumption while idle, with most of that consumed by istio-pilot. This is a problem since Istio is required for KNative development: I can't turn it off.
I am using 1.0.5 and see the same issue
kubectl describe nodes
istio-system istio-egressgateway-8666f9bdcc-ftf2h 10m (0%) 0 (0%) 0 (0%) 0 (0%)