kail icon indicating copy to clipboard operation
kail copied to clipboard

Requires a lot of CPU

Open d11wtq opened this issue 6 years ago • 2 comments

Is it expected that Kail would require 100% of a CPU? Can this be reduced by allowing the polling frequency to be lowered or something?

image

Nice project by the way.

d11wtq avatar Mar 14 '18 04:03 d11wtq

Hi @d11wtq. Thanks for the report.

No, it absolutely should not be using that much CPU. I have noticed this before when running on OSX while the same version on Linux did not. After spending a bit of time investigating I wrote it off as a fluke. Apparently that's not the case.

Would you mind adding a verbose log (--log-level debug --log-file debug.log) and a stack dump ctrl-\ from when it's behaving this way? edit: also go version and osx/devtools version please.

boz avatar Mar 14 '18 06:03 boz

Resurrecting an old issue, but I noticed that running kail was bumping up my local cluster's cpu usage by about 2x. Killing kail immediately dropped it. Running k8s in Docker Desktop on macos.

jscheel avatar Jun 26 '21 21:06 jscheel