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 idle CPU usage when enabling Kubernetes #3065

Open
siberex opened this Issue Jul 9, 2018 · 12 comments

Comments

Projects
None yet
@siberex
Copy link

siberex commented Jul 9, 2018

  • I have tried with the latest version of my channel (Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: CFEA972F-586B-4BD1-AE0C-BF698AA89BB6/20180709-130229

Expected behavior

Low idle CPU usage after enabling Kubernetes.

Actual behavior

High idle CPU usage after enabling Kubernetes (no matter with Kubernetes or Swarm selected as orchestrator).

Information

  • macOS Version: 10.13.5 (17F77), High Sierra

Diagnostic logs

Docker for Mac: version: 18.05.0-ce-mac67 (1fa4e2acfc1a52f79623add2390604515d32297e)
macOS: version 10.13.5 (build: 17F77)
logs: /tmp/CFEA972F-586B-4BD1-AE0C-BF698AA89BB6/20180709-130229.tar.gz
[OK]     vpnkit
[OK]     virtualization hypervisor
[OK]     vmnetd
[OK]     dns
[OK]     driver.amd64-linux
[OK]     virtualization VT-X
[OK]     app
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     kubernetes
[OK]     files
[OK]     env
[OK]     virtualization kern.hv_support
[OK]     osxfs
[OK]     moby-console
[OK]     logs
[OK]     docker-cli
[OK]     disk

Steps to reproduce the behavior

  1. Install latest edge branch Docker for Mac.
  2. Enable Kubernetes in Preferences (no matter with Kubernetes or Swarm selected as orchestrator).

Without adding any pods with kubectl and without creating any containers with docker, process com.docker.hyperkit starts eating a lot of CPU.

Disabling Kubernetes in Preferences solves the problem (com.docker.hyperkit returns to the normal idle behaviour with 1-2% CPU consuming).

@hori-ryota

This comment has been minimized.

@jodawill

This comment has been minimized.

Copy link

jodawill commented Jul 16, 2018

Same issue here. It makes my computer run hot and kills my battery.

@mehmetsalgar

This comment has been minimized.

Copy link

mehmetsalgar commented Jul 19, 2018

Same here, when I got it first I read some tips about increase the memory for Docker, reduce the number of assigned CPUs and remove unnecessary files sharing and using :cache in VOLUME statement in Dockerfile.

It helped for a while but today whike I like to test auto scale and one of the Deployment on Kubernetes did not started while 1 CPU was available, when I am gone 2 CPU again %100 load and going back to 1 CPU is not helping anymore.

@miro-kube

This comment has been minimized.

Copy link

miro-kube commented Jul 30, 2018

yes, it's an issue for me too, 30 to 40% cpu usage when idle
Version 18.06.0-ce-mac70, channel stable,

@hori-ryota

This comment has been minimized.

@zwing99

This comment has been minimized.

Copy link

zwing99 commented Aug 4, 2018

Yes please fix this!!!!

@atombender

This comment has been minimized.

Copy link

atombender commented Aug 13, 2018

Dupe of #2601.

@mlh758

This comment has been minimized.

Copy link

mlh758 commented Oct 12, 2018

I'm using Version 2.0.0.0-beta1-mac75 (27117) and I'm sitting at 391% CPU on my mac within seconds of turning on Kubernetes.

@pfriedland

This comment has been minimized.

Copy link

pfriedland commented Dec 16, 2018

yep. if I reduce the number of cores under Docker->Preferences->Advanced to something like '1', then the overall com.docker.hyperkit CPU utilization goes down proportionally. If I disable Kubernetes local cluster, the CPU utilization pretty much disappears from the Mac Activity Monitor. I think people have to buffer expectations when using k8s on a Mac with Docker. It should be for experimentation and minimal developer activities. Otherwise, use k8s in a real, provisioned environment to save your Mac from burning through CPU and the associated heat it generates.

@mlh758

This comment has been minimized.

Copy link

mlh758 commented Dec 16, 2018

I don’t see anywhere near this kind of utilization using minikube though. This is specific to Docker Kuberbetes.

@greenkiwi

This comment has been minimized.

Copy link

greenkiwi commented Dec 17, 2018

I see this pretty consistently:
Version 2.0.0.0-mac81 (29211)
Channel: stable
4271b9e6a8
Engine: 18.09.0
Machine: 0.16.0
Kubernetes: v1.10.3

@tvarwig

This comment has been minimized.

Copy link

tvarwig commented Jan 7, 2019

same issue. Specific to Docker kubernetes. Minikube does not do this.
Version 2.0.0.0-mac81 (29211)
Channel: stable
4271b9e6a8
Engine: 18.09.0
Kubernetes: v1.10.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment