beam.smp chewing CPU on v1.31.0 on arm

leewillis77 commented 3 weeks ago

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

I've upgraded to v1.31.0 and after the upgrade I noticed* that there's a beam.smp process chewing up CPU time:

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
 1041 10000     20   0  192432  64284   4732 S 144.9   3.4   6:13.18 beam.smp

The system is idle currently (car is asleep, and neither teslamate nor grafana are open on any devices).

It's possible this was happening before the latest upgrade - I can't say for sure.

Expected Behavior

System is idle with no excessive CPU hogging.

Steps To Reproduce

No response

Relevant log output

PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
 1041 10000     20   0  192432  64284   4732 S 144.9   3.4   6:13.18 beam.smp

Screenshots

No response

Additional data

No response

Type of installation

Docker

Version

v1.31.0

brianmay commented 3 weeks ago

Possibly this is not arm specific, but you notice it more on the slower processors.

JakobLichterfeld commented 3 weeks ago

OTP27 has various optimizations, wonder if one of these broke things for arm. https://www.erlang.org/blog/optimizations/

Actually a better explanation than mine, as

I assume the OTP27 docker image has set different compiler flags,

__

Possibly this is not arm specific, but you notice it more on the slower processors.

Yeah good point, currently I do not want dive to deep into this rabbit hole

teslamate-org / teslamate