# CPU load unexpectedly high after update

**URL:** <https://discourse.nodered.org/t/cpu-load-unexpectedly-high-after-update/80798>\
**Category:** General\
**Created:** [25 August 2023 14:29 UTC](https://discourse.nodered.org/t/cpu-load-unexpectedly-high-after-update/80798 "2023-08-25T14:29:15Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [25 August 2023 14:29 UTC](https://discourse.nodered.org/t/cpu-load-unexpectedly-high-after-update/80798/1 "2023-08-25T14:29:15Z")

</div>

Hi, today I´ve updated my RPi4, RPi2 (friend), Ubuntu VM.

On both Pi the CPU load is now unexpectedly high from Node-Red.

before, the load always stays at the red line:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/f/efd463686ce77f8f2e43898ff7886285c78f1136.png)

at my friends Pi:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/e/5ef9c81fb5e0b5af666c2d0c2c6256bc1d5e2e96.png)

we have nothing changed in Node-Red !  
just update/dist-upgrade.

any idea where to debug?

I tried on a 3rd RPi (without update today):

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/3/d366bb13cd21d279c96fd8cf9efa881a14aa3b6a.png)

It has just updated nodejs:  
_Entpacken von nodejs (18.17.1-deb-1nodesource1) über (18.17.0-deb-1nodesource1) ..._  
_nodejs (18.17.1-deb-1nodesource1) wird eingerichtet_

but here it is inconspicuous after the update:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/c/dcf90d50419d304b7dd39187c0e30d03bb503fd6.png)  
only slightly increased

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [25 August 2023 14:51 UTC](https://discourse.nodered.org/t/cpu-load-unexpectedly-high-after-update/80798/3 "2023-08-25T14:51:11Z")

</div>

It isn't clear what the lines on the chart are, and what has changed on the graph between before and after.

Have you looked to see what is consuming the CPU?

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [25 August 2023 14:54 UTC](https://discourse.nodered.org/t/cpu-load-unexpectedly-high-after-update/80798/4 "2023-08-25T14:54:31Z")

</div>

What was your aim in running sudo apt dist-upgrade?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [25 August 2023 15:15 UTC](https://discourse.nodered.org/t/cpu-load-unexpectedly-high-after-update/80798/5 "2023-08-25T15:15:14Z")

</div>

It is a good idea to keep systems up to date, particularly if they have access to the internet. Packages can have security updates applied and those should be picked up.

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [25 August 2023 15:39 UTC](https://discourse.nodered.org/t/cpu-load-unexpectedly-high-after-update/80798/6 "2023-08-25T15:39:41Z")

</div>

That's not the normally recommended command to update a Raspberry Pi though, hence my question.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [25 August 2023 15:47 UTC](https://discourse.nodered.org/t/cpu-load-unexpectedly-high-after-update/80798/7 "2023-08-25T15:47:14Z")

</div>

Oh I see, yes the modern command is `sudo apt full-upgrade` but the old style still works `sudo apt-get dist-upgrade` and for compatibility that has also been added to apt as `sudo apt dist-upgrade`. They all do the same thing as I understand it.

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [25 August 2023 16:45 UTC](https://discourse.nodered.org/t/cpu-load-unexpectedly-high-after-update/80798/8 "2023-08-25T16:45:36Z")

</div>

can I see within the process node-red, **who** is causing the high load?

the both RPi who has the high load use modbus contrib - the 3rd RPi who has no higher load today, hasn´t the modbus contrib.

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [25 August 2023 16:54 UTC](https://discourse.nodered.org/t/cpu-load-unexpectedly-high-after-update/80798/9 "2023-08-25T16:54:43Z")

</div>

I found the cause: Grafana Update.

I was the only one today.

Well wrong forum, thanks anyway.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [24 October 2023 16:55 UTC](https://discourse.nodered.org/t/cpu-load-unexpectedly-high-after-update/80798/10 "2023-10-24T16:55:03Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.