# \[ANNOUNCE\] node-red-contrib-v8-cpu-profiler: beta

**URL:** <https://discourse.nodered.org/t/announce-node-red-contrib-v8-cpu-profiler-beta/56017>\
**Category:** Share Your Nodes\
**Created:** [2 January 2022 23:20 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-v8-cpu-profiler-beta/56017 "2022-01-02T23:20:51Z")\
**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:** [4 January 2022 21:45 UTC](https://discourse.nodered.org/t/announce-node-red-contrib-v8-cpu-profiler-beta/56017/7 "2022-01-04T21:45:35Z")

</div>

Based on the [feedback](https://discourse.nodered.org/t/node-red-consuming-100-cpu-power/56006/19) from @IAmKonni, I have completely rewritten my wiki [tutorial](https://github.com/bartbutenaers/node-red-contrib-v8-cpu-profiler/wiki/Do-a-Node-RED-CPU-profiling-analysis-via-Chrome-Developer-Tools). It now explains a step-by-step about how to find the root cause of high CPU usage in a Node-RED flow.

---

_[View the full topic](https://discourse.nodered.org/t/announce-node-red-contrib-v8-cpu-profiler-beta/56017)._