CPU usage on PI4 is insane

metadalek · October 11, 2021 at 3:37 AM

On my pi4 2gb kodi.bin uses 30% CPU while idle. A quick use of strace shows why.

I assume this is a kodi issue rather than a libreelec issue?

Code

clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=915152499}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=915297869}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=918818221}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=918981518}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=919517703}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=919669480}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=919909203}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=920057925}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=920272221}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=920422110}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=920635629}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=920806462}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=920975629}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=921123962}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=921341036}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=921543795}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=922028925}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=922228055}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=922427666}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=922624036}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=922821332}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=923016055}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=923229777}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=923425073}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=923621129}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=924092425}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=924291332}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=924572240}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=924722110}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=925037758}) = 0
clock_gettime64(CLOCK_MONOTONIC, {tv_sec=968, tv_nsec=926112674}) = 0
clock_gettime64(CLOCK_MONOTONIC, {tv_sec=968, tv_nsec=926261785}) = 0
clock_gettime64(CLOCK_MONOTONIC, {tv_sec=968, tv_nsec=926405989}) = 0
clock_gettime64(CLOCK_MONOTONIC, {tv_sec=968, tv_nsec=926549618}) = 0
clock_gettime64(CLOCK_MONOTONIC, {tv_sec=968, tv_nsec=926724452}) = 0
clock_gettime64(CLOCK_MONOTONIC, {tv_sec=968, tv_nsec=926871989}) = 0
clock_gettime64(CLOCK_MONOTONIC, {tv_sec=968, tv_nsec=927044674}) = 0
clock_gettime64(CLOCK_MONOTONIC, {tv_sec=968, tv_nsec=927294711}) = 0
clock_gettime64(CLOCK_MONOTONIC, {tv_sec=968, tv_nsec=927455081}) = 0
clock_gettime64(CLOCK_MONOTONIC, {tv_sec=968, tv_nsec=927607174}) = 0
clock_gettime64(CLOCK_MONOTONIC, {tv_sec=968, tv_nsec=927758582}) = 0
clock_gettime64(CLOCK_MONOTONIC, {tv_sec=968, tv_nsec=927914489}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=956987240}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=957123036}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=957261277}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=957383740}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=957504832}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=963547740}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=963694980}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=963917332}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=964047592}) = 0
clock_gettime64(CLOCK_MONOTONIC_RAW, {tv_sec=968, tv_nsec=967207721}) = 0

Display More

chimpchump · October 11, 2021 at 3:54 AM

I would go through your installed add-on list and disable them one by one and observe any change in cpu behavior, by ssh'ing to your box and running top.

For example, I had a similar issue where my cpu was being smashed, and I found it was caused by the Library Watchdog add-on.

metadalek · October 11, 2021 at 4:20 AM

The only add on I have is amber skin. I have disabled that for testing. No change.

Halloway · October 11, 2021 at 8:54 AM

I checked my Pi4 and found similar results to yours - ~30% CPU usage at idle. I removed a redundant Aeon NOX skin and was then able to remove something called Library Data Provider. This brought it down to ~21%. I then removed a redundant Spotify add-on and that reduced by another couple of percent. My strace also provided similar data to yours.

20% still seems to me to be a little high, especially when the Windows laptop I'm typing this on will idle at around 1-3%. I suppose there's always the danger of comparing apples with oranges though.

**HiassofT** · October 11, 2021 at 12:24 PM

kodi.bin consuming about 15-20% on idle is quite normal on a clean install. Keep in mind that this is the percentage of a single core, RPi4 has 4 cores so it can go up to 400%. If you look at the "%Cpu(s)" summary in top you'll see about 95% idle.

Also keep in mind that the CPU frequency will have scaled down to 700MHz (check with bcmstat.sh or "vcgencmd measure_clock arm") and the load values reported from top are relative to that. So in absolute terms (4 cores at 1.5GHz max) kodi comsumes about 2.5% of available CPU resources.

Of course addons etc running in the background will consume CPU resources, so 20-30% (of a single core, at 700MHz) still look rather plausible.

so long,

Hias

CPU usage on PI4 is insane

Similar Threads

Cant play 4K MKV files without crashing

Raspberry Pi 4 - 4k 60hz and wifi 5ghz long standing issues solved -