# Node Red Install and Cleanup
**URL:** https://discourse.nodered.org/t/node-red-install-and-cleanup/5298
**Category:** General
**Created:** [29 November 2018 13:47 UTC](https://discourse.nodered.org/t/node-red-install-and-cleanup/5298 "2018-11-29T13:47:34Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Grendel61](https://discourse.nodered.org/u/Grendel61)
#### Post date: [29 November 2018 13:47 UTC](https://discourse.nodered.org/t/node-red-install-and-cleanup/5298/1 "2018-11-29T13:47:34Z")
We've been doing a lot of Node Red development with new nodes and flow development, and I think along the way I must have made some mistakes in the installation process. Node Red seems to function okay, but the deploy process takes 2-3 minutes to complete, and the chrome browser times out. I noticed using TOP that the CPU is maxed out during this process on Chrome.
The project itself is getting big, and eventually we will cut it up into physically smaller pieces, but I created a new project with an empty flow and it still has this problem.
I'm thinking this is a bigger problem related to node\_modules or something else. I was doing some npm linking on a new node before this happened, but I deleted that node. I also cleared the cache and did the the sudo install of node-red again, and an npm rebuild. However, it still has this problem.
I'm thinking that I should reinstall Node-Red, everything is backed up on GitHub. What is your recommendation to clean up?
Thanks in advance.
---
### Author:  [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [29 November 2018 16:41 UTC](https://discourse.nodered.org/t/node-red-install-and-cleanup/5298/2 "2018-11-29T16:41:58Z")
What do you have the deploy button set to?
If it is 'Full' try setting it to 'Modified Flows'
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [29 November 2018 20:16 UTC](https://discourse.nodered.org/t/node-red-install-and-cleanup/5298/3 "2018-11-29T20:16:01Z")
> [@Grendel61](#):
>
> I created a new project with an empty flow and it still has this problem.
Do you mean it takes minutes to deploy an empty flows file?
What hardware are you running on?
Post the node-red log from a restart, there may be a clue there.