Docker Community Forums

Share and learn in the Docker community.

Kitematic (Beta) using excessive CPU

beta

(andrew morton) #1

Expected behavior

Not seeing the management app using more CPU than the docker instances.

Actual behavior

When it’s running with no containers the CPU usage is 0%. Once you add a single active container the CPU usage starts to hover between 5-10% for the three apps:

  • Kinematic (Beta)
  • Kinematic (Beta)
  • Kinematic (Beta) Helper

If you start more containers it’ll often rise to 20%, 10%, 10%. Which is really annoying if you’re on a plane and trying to avoid killing your battery.

Information

  • the output of pinata diagnose -u on OSX:
OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta13.1
Running diagnostic tests:
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Docker logs are being collected into /tmp/20160531-125727.tar.gz
Most specific failure is: No error was detected
Your unique id is: 5C34DC8D-2FD1-4299-A836-AD6B432BC1E5
Please quote this in all correspondence.

Steps to reproduce the behavior

  1. Start a container
  2. Watch the CPU usage jump
  3. Stop the container
  4. Watch it return to 0%

(Alexandre) #2

Same here

4 running containers: Kitematic is using at least 30% of one CPU. 50% if WindowServer high CPU usage is caused by Kitematic, which seems to be the case - after closing Kitematic WindowServer dropped to <3% CPU.

OS X: version 10.11.5 (build: 15F34)
Docker.app: version v1.11.1-beta13.1
Running diagnostic tests:
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160602-102936.tar.gz
Most specific failure is: No error was detected

@drewish It is specific to Docker for Mac for you? E.g.: using the traditionnal VBox VM, is Kitematic CPU usage lower? I’m trying to see if this is caused by Docker for Mac or if it’s purely a Kitematic problem.


(andrew morton) #3

You know that’s a good question. I can’t check right now since I’d uninstalled VirtualBox. I’ll try to take a look on a coworker’s computer to see how it compares.