# Node Red consuming 100% CPU power

**URL:** <https://discourse.nodered.org/t/node-red-consuming-100-cpu-power/56006>\
**Category:** General\
**Created:** [2 January 2022 18:15 UTC](https://discourse.nodered.org/t/node-red-consuming-100-cpu-power/56006 "2022-01-02T18:15:44Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [2 January 2022 23:22 UTC](https://discourse.nodered.org/t/node-red-consuming-100-cpu-power/56006/7 "2022-01-02T23:22:46Z")

</div>

Hi @IAmKonni,

In case you don't manage to find the root cause (based on the extensive info that @Steve-Mcl already has given), could this be of any help to you perhaps:

> [@\[ANNOUNCE\] node-red-contrib-v8-cpu-profiler: beta](https://discourse.nodered.org/t/announce-node-red-contrib-v8-cpu-profiler-beta/56017):
>
> Hi folks, I saw tonight a [discussion](https://discourse.nodered.org/t/node-red-consuming-100-cpu-power) about CPU usage being 100% at irregular moments, which makes it very hard to figure out the root cause. Because: Since you don't know when it happens you cannot simply start a profiling, because you cannot let the profiling run for e.g. 3 days. Since we don't have continious profiling, like professional tools (e.g. Dynatrace) offer. So I thought: suppose we could start/stop cpu profiling from within a custom node. Then you can start/stop cpu profiling : …

Bart

---

_[View the full topic](https://discourse.nodered.org/t/node-red-consuming-100-cpu-power/56006)._
