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

high cpu usage with minikube #202

Open
dfang opened this issue Nov 21, 2017 · 6 comments
Open

high cpu usage with minikube #202

dfang opened this issue Nov 21, 2017 · 6 comments

Comments

@dfang
Copy link

dfang commented Nov 21, 2017

everytime i run minikube start, cpu usage increases to 100~300% and cpu fan gets loud ....

docker-machine-driver-xhyve version:
/usr/local/Cellar/docker-machine-driver-xhyve/0.3.3

minikube version
minikube version: v0.23.0

macOS version:
High sierra 10.13

@dfang dfang changed the title high cpu with minikube high cpu usage with minikube Nov 21, 2017
@komondor
Copy link

komondor commented Nov 22, 2017

did you try to increase the number of cpus allocated to the minikube vm ? Default is set to 2 cpus.

  • minikube start --vm-driver=xhyve --cpus NUMBER_OF_CPUS

I set mine to 4 and it reduced my cpu usage from 140% to 50%

@oyvindio
Copy link

You might be running into this minikube issue kubernetes/minikube#2130, try to disable the dashboard addon and see if that helps

@ProProgrammer
Copy link

On:
macOS Sierra - 10.12.6
minikube: v0.23.0

When starting minikube without adding --cpus 4 with dashboard addon enabled, its always over 100% usage as reported in this issue. However when I disable the dashboard addon as suggested by @oyvindio, the usage falls to around 33%

After trying @komondor's suggestion minikube start --vm-driver=xhyve --cpus 4 with dashboard addon enabled, the CPU usage fluctuates around 24 - 28% and rarely goes above 40%.

However, not sure if allowing 4 CPUs can cause any issue with my machine otherwise. Would it?

@Blacksheepi
Copy link

same problem

@fnasser
Copy link

fnasser commented Feb 7, 2019

Same problem with Minishift

After a couple of hours if the minishift is not stopped the computer will trash (both cpu and memory very high for docker-machine-driver-xhyve) and needs to be rebooted, so 2 hrs is the limit for usage.

There is no kubernetes dashboard involved, so I guess it was not the culprit.

@americanexplorer13
Copy link

@fnasser

Have you solved it?

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

7 participants