Help tracking down the culprit of high CPU usage with Hassio

I am running the latest release of Hassio (currently 0.82.1) and over the past week or so I have noticed increased instability and high CPU usage with my install. CPU utilization used to be around 4-6%, but now it is hovering around 29-39%. I have tried stopping various add-ons including the Mosquitto broker and NodeRed, but this doesn’t seem to make a difference.

I’m seeing a high volume of web socket errors and my Dark Sky sensor periodically disappears until I refresh my API key on the Dark Sky dashboard and re-enter it in my config. (I am nowhere near the API daily usage limit). I’m on mobile right now but I can post logs later from a computer if that will help.

I’ve also noticed some “spontaneous” reboots and some instances where components “disappear.” On the Hassio info (i) tab, after a reboot, sometimes the system shows 78 components loaded and other times 83.

Is there any way to monitor which add-on or component is causing the high CPU usage and instability? I was thinking of trying to monitor the different docker containers, but I couldn’t figure out if that is possible on a vanilla install of Hassio. (I do have the SSH add-on installed.)

Thanks in advance for any recommendations.

I;m getting something similar running the latest 0.83 HA under Hassio, I used to have 2-5% CPU usage on my RPi 3 on 0.81, now its at 20-30% since updating to the latest everything.

Try running top using SSH, you should see somthing like this:

Mem: 487372K used, 460980K free, 684K shrd, 93504K buff, 184880K cached
CPU:  7.9% usr 17.4% sys  0.0% nic 74.5% idle  0.0% io  0.0% irq  0.0% sirq
Load average: 1.01 1.03 0.98 2/303 1779
  835   814 root     R     157m 16.9   1 25.1 /usr/local/bin/python3 -m homeassistant --config /config
  306   297 root     S     921m 99.3   0  0.1 docker-containerd --config /var/run/docker/containerd/containerd.toml
  297     1 root     S    1509m162.7   3  0.0 /usr/bin/dockerd -H fd:// --st
1 Like

Thanks for the suggestion. I’ll remember top.

For the moment things seem to have calmed down under 0.83.2, but I suppose time will tell.

I had a similar issue yesterday and found the culprit to be the SSH HASSIO Addon.