# Extremely slow loading of GUI

**URL:** <https://discourse.nodered.org/t/extremely-slow-loading-of-gui/10955>\
**Category:** General\
**Created:** [9 May 2019 13:51 UTC](https://discourse.nodered.org/t/extremely-slow-loading-of-gui/10955 "2019-05-09T13:51:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![awasen](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/awasen/32/596_2.png) [@awasen](https://discourse.nodered.org/u/awasen)\
**Post date:** [9 May 2019 13:51 UTC](https://discourse.nodered.org/t/extremely-slow-loading-of-gui/10955/1 "2019-05-09T13:51:27Z")

</div>

> 9 May 15:42:07 - [info]
> 
> # Welcome to Node-RED
> 
> 9 May 15:42:07 - [info] Node-RED version: v0.20.5  
> 9 May 15:42:07 - [info] Node.js version: v10.15.3  
> 9 May 15:42:07 - [info] Linux 4.14.98-v7+ arm LE  
> 9 May 15:42:09 - [info] Loading palette nodes  
> 9 May 15:42:23 - [info] Dashboard version 2.8.0 started at /ui  
> 9 May 15:42:25 - [info] Settings file : /home/pi/.node-red/settings.js  
> 9 May 15:42:25 - [info] Context store : 'default' [module=memory]  
> 9 May 15:42:25 - [info] User directory : /home/pi/.node-red  
> 9 May 15:42:25 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable  
> 9 May 15:42:25 - [info] Flows file : /home/pi/.node-red/flows\_raspberrypi.json  
> 9 May 15:42:25 - [error] Unable to listen on [http://127.0.0.1:1880/](http://127.0.0.1:1880/)  
> 9 May 15:42:25 - [error] Error: port in use

Running on a (freshly upgraded) RPi 3B+ and updated node-red/Node.js.

Trying to open the Web-gui of admin/development takes a veeeery long time (\>10 minutes). Max Memory is set for RPi according to the recommendations.

Opening the browser is fine, all other programs are fine and the node-red functions are running (I have temperatures doing POST to other server and it is getting updated) so it seems only the Web-gui is slow (also dashboard isn't loading).

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/2/20157d7eae0eab9d3b874e03e07596aa69c4acb2.png)  
As seen in the screen grab the resources are not exhaused...

There's a lot of different node-red processes running though so I am not sure if that is normal:

> pi@raspberrypi:~ $ ps -ef | grep node  
> pi 317 1 59 09:16 ? 03:45:45 node-red  
> pi 825 317 0 09:16 ? 00:00:00 /bin/bash /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio out 13 0  
> pi 827 317 0 09:16 ? 00:00:00 /bin/bash /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio out 29 0  
> pi 828 825 0 09:16 ? 00:00:00 python -u /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio.py out 13 0  
> pi 830 317 0 09:16 ? 00:00:00 /bin/bash /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio out 15 0  
> pi 831 827 0 09:16 ? 00:00:00 python -u /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio.py out 29 0  
> pi 833 317 0 09:16 ? 00:00:00 /bin/bash /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio out 31 0  
> pi 834 830 0 09:16 ? 00:00:00 python -u /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio.py out 15 0  
> pi 836 317 0 09:16 ? 00:00:00 /bin/bash /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio in 40 tri 25  
> pi 837 833 0 09:16 ? 00:00:00 python -u /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio.py out 31 0  
> pi 839 836 0 09:16 ? 00:00:00 python -u /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio.py in 40 tri 25  
> pi 840 317 0 09:16 ? 00:00:00 /bin/bash /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio in 38 tri 25  
> pi 842 840 0 09:16 ? 00:00:00 python -u /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio.py in 38 tri 25  
> pi 843 317 0 09:16 ? 00:00:00 /bin/bash /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio in 36 tri 25  
> pi 845 843 0 09:16 ? 00:00:00 python -u /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio.py in 36 tri 25  
> pi 846 317 0 09:16 ? 00:00:00 /bin/bash /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio in 37 tri 25  
> pi 851 846 0 09:16 ? 00:00:00 python -u /usr/lib/node\_modules/node-red/node\_modules/@node-red/nodes/core/hardware/nrgpio.py in 37 tri 25

What can I check?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [9 May 2019 14:56 UTC](https://discourse.nodered.org/t/extremely-slow-loading-of-gui/10955/2 "2019-05-09T14:56:47Z")

</div>

> [@awasen](#):
>
> rying to open the Web-gui of admin/development takes a veeeery long time (\>10 minutes).

Have you checked the browsers javascript console for any error messages? Similarly the 'Network' tab will show which http requests are taking a long time.

If you use a browser from another machine to access Node-RED remotely is there any improvement?

Do you have a lot of nodes in your flow?

Can you look in `/home/pi/.node-red/lib` and let us know if there are lots of files under there?

---

<div class="post-metadata">

**Author:** ![awasen](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/awasen/32/596_2.png) [@awasen](https://discourse.nodered.org/u/awasen)\
**Post date:** [9 May 2019 15:02 UTC](https://discourse.nodered.org/t/extremely-slow-loading-of-gui/10955/3 "2019-05-09T15:02:43Z")

</div>

Thanks for getting back to me! Much appreciated!

As for Console errors, there are none:  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/4/49dec83030271bd5a954715da080eddb8a585741.png)

> pi@raspberrypi:~/.node-red/lib $ ls -la  
> total 12  
> drwxr-xr-x 3 pi pi 4096 Feb 8 2018 .  
> drwxr-xr-x 4 pi pi 4096 May 7 21:01 ..  
> drwxr-xr-x 2 pi pi 4096 Feb 8 2018 flows

There's no files under the directory, just a "flows" directory.

There are maybe 40 something nodes in total and a few (20 maybe) UI nodes (gauges mostly)

---

<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:** [9 May 2019 22:58 UTC](https://discourse.nodered.org/t/extremely-slow-loading-of-gui/10955/4 "2019-05-09T22:58:45Z")

</div>

> [@knolleary](#):
>
> If you use a browser from another machine to access Node-RED remotely is there any improvement?

@awasen, have you tried accessing node red from another computer as suggested? Running a browser on a pi is fairly heavy lifting.

---

<div class="post-metadata">

**Author:** ![awasen](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/awasen/32/596_2.png) [@awasen](https://discourse.nodered.org/u/awasen)\
**Post date:** [10 May 2019 05:35 UTC](https://discourse.nodered.org/t/extremely-slow-loading-of-gui/10955/5 "2019-05-10T05:35:17Z")

</div>

Yes, tried from other computers, it was one of the first things that hit me... 🙂  
Still the same problem though...

Although normal "surfing" works fine it's responsive and running nicely. It's only the NR web-gui lagging...