# Successive deployments increase CPU load

**URL:** <https://discourse.nodered.org/t/successive-deployments-increase-cpu-load/9202>\
**Category:** General\
**Created:** [19 March 2019 20:11 UTC](https://discourse.nodered.org/t/successive-deployments-increase-cpu-load/9202 "2019-03-19T20:11:32Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [20 March 2019 13:43 UTC](https://discourse.nodered.org/t/successive-deployments-increase-cpu-load/9202/21 "2019-03-20T13:43:33Z")

</div>

> [@guardiande](#):
>
> I suspect the configuration nodes to cause the increase.

You've shared the list of nodes you have installed, but what really matters are the nodes you are actually using. You've mentioned a couple, but could you provide a more complete list?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [20 March 2019 13:49 UTC](https://discourse.nodered.org/t/successive-deployments-increase-cpu-load/9202/22 "2019-03-20T13:49:36Z")

</div>

though some (badly behaved) nodes could install things globally on load that consume resources and then obviously never respond to a close event, regardless of if used in the flow or not.

---

<div class="post-metadata">

**Author:** ![guardiande](https://avatars.discourse-cdn.com/v4/letter/g/e0b2c6/32.png) [@guardiande](https://discourse.nodered.org/u/guardiande)\
**Post date:** [20 March 2019 17:40 UTC](https://discourse.nodered.org/t/successive-deployments-increase-cpu-load/9202/23 "2019-03-20T17:40:02Z")

</div>

> [@knolleary](#):
>
> You've mentioned a couple, but could you provide a more complete list?

Of course:

```auto
"type":"alexa-local"
"type":"better-sonos-config"
"type":"better-sonos-control"
"type":"catch"
"type":"change"
"type":"comment"
"type":"debug"
"type":"delay"
"type":"function"
"type":"http request"
"type":"hue-bridge"
"type":"hue-group"
"type":"hue-light"
"type":"influxdb"
"type":"influxdb in"
"type":"inject"
"type":"join"
"type":"json"
"type":"lgtv-app"
"type":"lgtv-button"
"type":"lgtv-channel"
"type":"lgtv-config"
"type":"lgtv-toast"
"type":"light-scheduler-settings"
"type":"link in"
"type":"link out"
"type":"mqtt-broker"
"type":"mqtt in"
"type":"mqtt out"
"type":"openhab2-controller"
"type":"openhab2-get"
"type":"openhab2-in"
"type":"openhab2-out"
"type":"persist in"
"type":"persist out"
"type":"persist-store"
"type":"pushover api"
"type":"pushover-keys"
"type":"schedex"
"type":"split"
"type":"status"
"type":"str"
"type":"switch"
"type":"tab"
"type":"template"
"type":"ui_base"
"type":"ui_colour_picker"
"type":"ui_group"
"type":"ui_numeric"
"type":"ui_slider"
"type":"ui_switch"
"type":"ui_tab"
"type":"ui_text"
"type":"ui_text_input"

```

---

<div class="post-metadata">

**Author:** ![spants](https://avatars.discourse-cdn.com/v4/letter/s/73ab20/32.png) [@spants](https://discourse.nodered.org/u/spants)\
**Post date:** [8 April 2019 09:00 UTC](https://discourse.nodered.org/t/successive-deployments-increase-cpu-load/9202/24 "2019-04-08T09:00:04Z")

</div>

May or may not be relevant, but I had to remove LGTV node from my Node RED instance as it hard crashed Node RED with node v10.... Try removing this node and see if the problem still happens.  
(I have reported the error to LGTV github)

---

<div class="post-metadata">

**Author:** ![andyw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/andyw/32/36669_2.png) [@andyw](https://discourse.nodered.org/u/andyw)\
**Post date:** [6 February 2021 20:51 UTC](https://discourse.nodered.org/t/successive-deployments-increase-cpu-load/9202/25 "2021-02-06T20:51:06Z")

</div>

I'm seeing a similar issue with my RPi3 Node-RED / Domoticz setup.

Domoticz reports average CPU load of 10%. Last week before I updated some nodes the load was \<3%. But what is weird is restarting Node-RED and the load returns to \<3% until I deploy when it jumps to 10%.  
Something isn't happy....

It turns out node-red-contrib-alexa-remote2 is causing the problem, see ["On device activity" not working anymore · Issue #193 · 586837r/node-red-contrib-alexa-remote2 · GitHub](https://github.com/586837r/node-red-contrib-alexa-remote2/issues/193#issuecomment-772466561)

[Previous page](https://discourse.nodered.org/t/successive-deployments-increase-cpu-load/9202.md?page=1)