Hi , Is there any performance stats vis-à-vis size of flows.json? We have ~3500 nodes in flows .json - spanning multiple flows / subflows. What we see is - once we do deploy - even if its deploy modified nodes - it takes significant time (more than few mins) for runtime to be available again. Du…

[image] ghayne: What hardware are you running on? Let me check this and come back. Will take some time to connect to that piece since its at work. [image] Steve-Mcl: and you can multiple the number of nodes in each subflow by the number of instances Agree. Did not think of that. So i…

I would certainly check the usual suspects such as exceeding your actual memory and therefore getting lots of paging - that will kill any performance. Also check whether it is Node-RED causing that or something else such as MongoDB. Personally, I would also look to collapse some of the multiple-nod…

[image] Steve-Mcl: That doesnt seem right - is that all node types or certain node types? and are you modifying a node inside a subflow or main flow? I did the test. Created inject + debug on tab / main flow. No subflows changes. Changed only the position of debug flag Clicked Deploy Nodes D…

If you enable trace level logging in the runtime you will get much more detailed information about starting/stopping individual nodes. With so many nodes that will be a lot of information, but it's also the best way to try to see where time is being spent.

[image] SandeepA: Is there some trace or something which can help me investigate what the system is doing during those 8 mins ? I always do cpu profiling in those cases. See here for more info. Be aware that analysing the profiling result is not always easy...

[image] knolleary: If you enable trace level logging in the runtime you will get much more detailed information about starting/stopping individual nodes. With so many nodes that will be a lot of information, but it's also the best way to try to see where time is being spent. Thank You Nick. …

[image] SandeepA: Is this the .. Yes - you want to set logging.console.level to trace

[image] SandeepA: I did the test. Created inject + debug on tab / main flow. No subflows changes. Changed only the position of debug flag Clicked Deploy Nodes Deployed finished immediately I assume "2. Clicked Deploy Nodes" means you were in "Modified Nodes" deploy mode? Since it deployed …

[image] knolleary: Yes - you want to set logging.console.level to trace Thanks. Will do . Will come back. Work machine ... some of these changes take longer than needed. [image] Steve-Mcl: I assume "2. Clicked Deploy Nodes" means you were in "Modified Nodes" deploy mode? Yes. That's t…

better still, set the inject to repeat every 2 seconds - then check console after deploy.

Node-RED

Node-RED Forum

Size of flows.json and performance

General

Steve-Mcl 13 June 2022 19:21 18

Yes

See here: Node-RED v0.19.4 3 minute delay during startup on windows - #15 by Steve-Mcl

Topic		Replies	Views
Deployment time is long General	22	1317	2 March 2021
NR flows update very slow when >> 500 flows General	13	654	6 May 2024
Deploy takes very long - sometimes as much as 50 mins General	35	820	28 May 2023
Node red processing slowed General docker , function-node , flows	22	775	6 December 2025
Node-RED docker container long startup/deployment time General docker	2	223	6 October 2023

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.

Size of flows.json and performance

Related topics