Zubair Lutfullah Kakakhel

This is probably due to https://github.com/balena-io/balena-supervisor/issues/861 which has been fixed now. And this supervisor is in the development branch and will be in next release.

Here is a graph of cpu usage using telegraf/influxdb/grafana  balenaOS cpu usage is spiky. Unless I'm mistaken that is due to the various healthchecks (supervisor/balenad being the most cpu...

We can investigate lighter-weight health-checks or perhaps make the healthcheck frequency user configurable

Another test to isolate the increase in bw would be to use fin 2.45 but remove new supervisor and run the old 2.38 supervisor. That way we'll know if something...

pi0w, no app container, 2.29.2 even after 5 minutes, the supervisor and balena daemon seem to be doing something ``` Mem: 254004K used, 237460K free, 3864K shrd, 19484K buff, 100412K...

So cpu load is unusually high on my pi0 on balenaOS `15:09:46 up 0:15, 1 user, load average: 0.78, 0.84, 0.66` Its sensible on pi0 on raspbian lite. `15:16:54 up...

note to self: check out health monitoring using netdata.

Thread: https://www.flowdock.com/app/rulemotion/r-resinos/threads/Kte3kY0fLVhskQtAHQDo0qIhmNU

@Jaeyoung-Lim yes quite a few pull requests are on their way/happening. The work is tracked in https://github.com/balena-os/meta-balena/issues/946

@SloMusti quite a few pull requests are on their way to improve boot time. The work is tracked in https://github.com/balena-os/meta-balena/issues/946