search

machine-drivers / docker-machine-driver-xhyve

docker-machine/minikube/minishift driver plugin for xhyve/hyperkit (native macOS hypervisor.framework)
https://godoc.org/github.com/machine-drivers/docker-machine-driver-xhyve
BSD 3-Clause "New" or "Revised" License
889 stars 73 forks source link

high cpu usage with minikube #202

Open dfang opened 6 years ago

dfang commented 6 years ago

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

komondor commented 6 years ago

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

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

oyvindio commented 6 years ago

You might be running into this minikube issue https://github.com/kubernetes/minikube/issues/2130, try to disable the dashboard addon and see if that helps

ProProgrammer commented 6 years ago

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 commented 6 years ago

same problem

fnasser commented 5 years ago

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 commented 6 months ago

@fnasser

Have you solved it?