# Node-RED docker container long startup/deployment time

**URL:** <https://discourse.nodered.org/t/node-red-docker-container-long-startup-deployment-time/81827>\
**Category:** General\
**Tags:** docker\
**Created:** [6 October 2023 11:26 UTC](https://discourse.nodered.org/t/node-red-docker-container-long-startup-deployment-time/81827 "2023-10-06T11:26:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [6 October 2023 12:13 UTC](https://discourse.nodered.org/t/node-red-docker-container-long-startup-deployment-time/81827/2 "2023-10-06T12:13:24Z")

</div>

Of course more nodes will make things slower to load and edit.

You didn't say what kind of deploy you were doing. If you are doing a full deploy then all of your nodes are destroyed and recreated every time, even if you edit just one single thing.

Have a look at this thread. I've linked you to the comment I made about subflows and how there are far more things happening than you might realise.

> [@Deploy takes very long - sometimes as much as 50 mins](https://discourse.nodered.org/t/deploy-takes-very-long-sometimes-as-much-as-50-mins/78403/17):
>
> and this gets worse if your subflows nest subflows. each instance creates all its internal nodes and if any of those are subflow instances, they are created too. It really doesnt take much to get to huge numbers Example: Subflow1: 10 regular nodes, 5 Subflow2 nodes Subflow2: 20 regular nodes Main flows: use 100 Subflow1s and 100 regular nodes this means 100 + (100 \* (10 + (5 \* 20))) == 11100 nodes to be created, setup, initialised etc etc. Contrast that with link-calls (aka pure funct…

But you should read the entire thread.

---

_[View the full topic](https://discourse.nodered.org/t/node-red-docker-container-long-startup-deployment-time/81827)._