Hi folks, I saw tonight a discussion 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…

Hey Bart, thanks a lot, I installed the module. Is it enough to place it in a single flow? Do I need any input/output connections (e.g. an inject?)? Where can I find the .cpuprofile file? Is it written to ./node-red? I can give you feedback probably tomorrow. :slight_smile:

Okay, I answered most of the questions by reading your github page ... :wink: bartbutenaers/node-red-contrib-v8-cpu-profiler/blob/main/README.md # node-red-contrib-v8-cpu-profiler A Node-RED node to start CPU profiling on the V8 engine (used by NodeJs). ## Install Run the following np…

Hi Mathias, Yes a single node is enough, since it connects to the Google V8 Javascript engine (that runs your NodeJs server). So it will profile ALL the Javascript code that is being executed in your NodeJs instance. On my readme page you can find an example flow, which shows how to start/sto…

I got an output - it worked so far. I could import it into the chrome dev tools. Thank you very much for this node - now I just need some expertise to interpret the data. =P

[image] IAmKonni: I just need some expertise to interpret the data Yes indeed it is not very easy to start with interpreting flame graphs. I have added a few tips on my wiki , but I am not an expert in this. If you find anything useful, please share it so I can add it to the wiki... Or if y…

I have added two new features: When a profile is complete, it will be send on a first output. But when a profile is interrupted prematurely, it will be send on a second output. The output message now contains both the startTimestamp and endTimestamp. These changes allowed me to write a new tutor…

Version 1.0.0 is good enough for me as an initial version: [image]

Hey there, I am having ultra high load permanently and woanted to check it out with your node. Nodered runs under Docker, which itself is under Ubuntu VM (Proxmox). I get this error when deploying your sample flow: 2 Jul 20:01:30 - [info] - node-red-contrib-v8-cpu-profiler:v8-cpu-profiler : Er…

I found out, that the high load came from some MQTT node, that could not reach the Broker. Still have no clue, why that would produce such shift load though.

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

Share Your Nodes

BartButenaers 4 January 2022 21:45 7

Based on the feedback from @IAmKonni, I have completely rewritten my wiki tutorial. It now explains a step-by-step about how to find the root cause of high CPU usage in a Node-RED flow.

Topic		Replies	Views
Cpu profiling a single node: collecting ideas Feature Requests	16	922	9 February 2022
Profiling flows with ClinicJs to analyze CPU performance issues Share Your Projects	2	880	13 December 2021
Performance profiling and observability Developing Nodes	13	1107	14 January 2023
[ANNOUNCE] node-red-contrib-msg-profiler: 1.0.0 beta Share Your Nodes	12	1571	5 December 2021
CPU Usage spikes - how to identify problems General	9	5694	19 March 2022

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

Related topics