# NodeRed Console Log / CPU Mem per flow

**URL:** <https://discourse.nodered.org/t/nodered-console-log-cpu-mem-per-flow/61967>\
**Category:** General\
**Created:** [29 April 2022 15:42 UTC](https://discourse.nodered.org/t/nodered-console-log-cpu-mem-per-flow/61967 "2022-04-29T15:42:46Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [29 April 2022 16:19 UTC](https://discourse.nodered.org/t/nodered-console-log-cpu-mem-per-flow/61967/2 "2022-04-29T16:19:26Z")

</div>

Hi @sourceminer,  
Perhaps others have found better ways to do this...

But the most interesting stuff I have found is described [here](https://discourse.nodered.org/t/profiling-flows-with-clinicjs-to-analyze-cpu-performance-issues/55139). The disadvantage is that you need to start Node-RED via ClinicJs, and the result is only analyzed after you close it again. So it is no real time monitoring that you can attach to a running Node-RED instance unfortunately.

From what I have read so far, I don't think it is possible to do live monitoring of cpu/memory per node or flow. In case you would like to digg in technical debt, see [here](https://github.com/node-red/designs/discussions/71) for more background info. Warning: it is no bedtime literature 🙂

But of course I might be mistaken...  
Bart

---

_[View the full topic](https://discourse.nodered.org/t/nodered-console-log-cpu-mem-per-flow/61967)._