Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requires a lot of CPU #18

Open
d11wtq opened this issue Mar 14, 2018 · 2 comments
Open

Requires a lot of CPU #18

d11wtq opened this issue Mar 14, 2018 · 2 comments

Comments

@d11wtq
Copy link

d11wtq commented Mar 14, 2018

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.

@boz
Copy link
Owner

boz commented Mar 14, 2018

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.

@jscheel
Copy link

jscheel commented Jun 26, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants