Hi All, I am facing an issue where the custom nodes written by me (they constantly poll s3 to watch for latest files & also polls database to look for change in file ingestion status after running ETL Jobs on files) are consuming high CPU reaching almost 100%. [container-cpu] I have read on this …

@Colin ... Thanks for the reply. The memory doesn't jump in immediately, it takes a while sometime 4-8 hrs, sometimes a day or more ... so my guess is based on the number of nodes polling both s3 & DB ...the time is varying. More nodes means quick jump and less nodes may take more time. So I deploye…

At the moment, the only graph you've shared is of CPU usage and you've assumed that is caused by memory usage. Have you got an equivalent graph of memory usage to show that really is the issue at hand?

@TotallyInformation ...I agree with your post and I am already using best practices laid down for JS coding though I have not worked with NodeJs ever before, but all programming languages have same basics so syntactical difference doesn't matter. Just listing them down so that anyone else reading h…

@knolleary ... I was not having access to the graphs. That graph was shared by dev-ops team. I have taken access today and after today's refactoring I don't see very high memory usage ....here is the graph for memory usage from today. [node-red-mem] Can u plz help me understand what could cause C…

I think it more likely that you are doing more work that you think in your flows. You mentioned that you query a database. How often do you do that, how many rows does your query return, and what processing are you running on the data?

[image] BShashwat: Also I don't think Javascript passes by reference . It passes by value, just that if any objects are getting passed as parameters they retain reference to values i.e. new copy will refer to old values An interesting view. from that Q: It's always pass by value, but for ob…

@TotallyInformation .... posting one of my node code here ... I will delete it later once u have seen this. The code is pretty simple it authenticates user, reads metadata from DB based on custom code to run (setup from UI so that metadata has info about which connection to use for warehouse, wh…

Please identify which line is which on the chart.

@Colin ... Chart has legend which displays the following: Creamish color line is Node-Red container Purplish blue line is ETL container Green color line are REST API container Yellow colored line was previous Node-Red container which was fully spiked and got killed when I deployed new Node-Red co…

So what problem in that chart are you trying to address?

Node-RED

Node-RED Forum

Reclaiming memory from Nodes

Developing Nodes

Topic		Replies	Views
Node-red application gradually increases memory usage until crashing General	15	3233	11 April 2021
Memory leak, none of the existing answers help General	13	449	5 April 2021
Memory leak ?... trouble performance now General	36	2471	13 February 2022
Memory leak, what am I doing wrong? General	28	11342	10 December 2018
How Node-red's memory recycling mechanism works General	39	774	16 March 2024

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Reclaiming memory from Nodes

Related topics