# Dashboard slow to load

**URL:** <https://discourse.nodered.org/t/dashboard-slow-to-load/84993>\
**Category:** Dashboard\
**Created:** [28 January 2024 17:05 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993 "2024-01-28T17:05:53Z")\
**Posts on this page:** 13\
**Page:** 2

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [29 January 2024 17:17 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/22 "2024-01-29T17:17:11Z")

</div>

And the network tab in the browser?

Also what does top show when not loading the dashboard? I would like to see the memory stuff as well as the top few lines of processes please.

---

<div class="post-metadata">

**Author:** ![TheSaltydog](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@TheSaltydog](https://discourse.nodered.org/u/TheSaltydog)\
**Post date:** [29 January 2024 19:33 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/23 "2024-01-29T19:33:56Z")

</div>

Attaching the Network tab and a screen of `top` during normal operations.

 ![Screenshot 2024-01-29 alle 20.31.14](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/d/fda3900757840399b94278f33fb0a3bbd2755c10.jpeg)  
 ![Screenshot 2024-01-29 alle 20.32.30](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/6/16eb44f9412cad1dc5b1b13dfbd1ce1e446465ef.png)

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [29 January 2024 20:25 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/24 "2024-01-29T20:25:48Z")

</div>

Node-RED is using 30% of your memory which is a bit insane I think.

You seem to be running on a 1GB RAM device and something is causing some swap and this is quite likely to be part of the issue. Swap activity on an older Pi running from SD-Card is a performance killer.

---

<div class="post-metadata">

**Author:** ![TheSaltydog](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@TheSaltydog](https://discourse.nodered.org/u/TheSaltydog)\
**Post date:** [29 January 2024 20:42 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/25 "2024-01-29T20:42:15Z")

</div>

> [@TotallyInformation](#):
>
> Node-RED is using 30% of your memory which is a bit insane I think.

I think so too, but what to do?

> [@TotallyInformation](#):
>
> You seem to be running on a 1GB RAM

Yes

> [@TotallyInformation](#):
>
> something is causing some swap

This PI is only running NR (with mosquitto)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [29 January 2024 20:49 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/26 "2024-01-29T20:49:00Z")

</div>

> [@TheSaltydog](#):
>
> I think so too, but what to do?

Upgrade to a 2GB (or more) Pi4. That should make a big difference. Or something like an old laptop you may have lying around if it doesn't need to be a pi.

From the network tab I was hoping to see something like

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/1/f1e13d4143d905ee38d3c6ecfc4cb5ecbfcc7f65.png)

to get an idea of how much is being transferred and how long it takes.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [29 January 2024 21:29 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/27 "2024-01-29T21:29:45Z")

</div>

> [@TheSaltydog](#):
>
> I think so too, but what to do?

I think you need to review your flows. Look for over-use of sub-flows and check for loops.

---

<div class="post-metadata">

**Author:** ![TheSaltydog](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@TheSaltydog](https://discourse.nodered.org/u/TheSaltydog)\
**Post date:** [29 January 2024 21:51 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/28 "2024-01-29T21:51:04Z")

</div>

> [@Colin](#):
>
> From the network tab I was hoping to see something like

here it is a better view

 ![Screenshot 2024-01-29 alle 22.49.27](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/2/628301b0abb5c20a4bcfccf7f32fd666d0cf3978.png)

---

<div class="post-metadata">

**Author:** ![TheSaltydog](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@TheSaltydog](https://discourse.nodered.org/u/TheSaltydog)\
**Post date:** [29 January 2024 21:54 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/29 "2024-01-29T21:54:10Z")

</div>

> [@Colin](#):
>
> Upgrade to a 2GB (or more) Pi4. That should make a big difference. Or something like an old laptop you may have lying around if it doesn't need to be a pi.

Yes, I think this is the idea. I am start thinking about it

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [29 January 2024 22:05 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/30 "2024-01-29T22:05:02Z")

</div>

What is the connection between the browser and the Pi? You only seem to be getting about 1Mbps, if I am reading the tools output correctly.

---

<div class="post-metadata">

**Author:** ![TheSaltydog](https://avatars.discourse-cdn.com/v4/letter/t/47e85d/32.png) [@TheSaltydog](https://discourse.nodered.org/u/TheSaltydog)\
**Post date:** [30 January 2024 16:38 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/31 "2024-01-30T16:38:01Z")

</div>

> [@Colin](#):
>
> You only seem to be getting about 1Mbps

@Colin Aaah! Yes, you got the point! I changed the ethernet cable between Raspi and the switch and now it is fast again! Thank you for helping in troubleshooting.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [30 January 2024 20:48 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/32 "2024-01-30T20:48:25Z")

</div>

I had something a bit similar recently. I think one wire had gone open circuit but Ethernet can still get something through even with one wire open. The comms had to continually retry though, due to comms error, so the pi was working flat out continually re-sending packets.

---

<div class="post-metadata">

**Author:** ![thebaldgeek](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thebaldgeek/32/93523_2.png) [@thebaldgeek](https://discourse.nodered.org/u/thebaldgeek)\
**Post date:** [2 February 2024 22:23 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/33 "2024-02-02T22:23:53Z")

</div>

@TheSaltydog You might find my thread here about the slow loading / timeout happy dashboard.

> [@How to make Dashboard webserver more robust?](https://discourse.nodered.org/t/how-to-make-dashboard-webserver-more-robust/61295):
>
> My users keep getting "Connection lost" message in the top right corner of the dashboard and shortly thereafter the site refreshes on them. [image] Node-RED Dashboard is here: [https://acars.adsbexchange.com/](https://acars.adsbexchange.com/) I have moved my site between data centers, the latter is the most robust that has hosted the site and I am still seeing the error. Seeing around 720 Gb of upload traffic every 24 hours. Is there any way I can find out how many people are connected at any one time? Whats the webserver t…

There are many tips that you might be able to use to speed things up, but given your Pi platform, I think the others have covered those limitations.  
My NR was running on a 12 core 128Gb RAM gaming class PC and takes around 2 minutes to load my dash.

IMHO the V2 dash should not be out of alpha yet, its still mostly unusable due to lack of core features, so you will need to go down that path very carefully knowing that its a waiting game for the features to catch up with the v1 dash.  
I am unable to migrate any of my current dash features over so can not make any speed / robustness comparisons as yet.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [16 February 2024 22:24 UTC](https://discourse.nodered.org/t/dashboard-slow-to-load/84993/34 "2024-02-16T22:24:28Z")

</div>

Closed on 16 February 2024 22:24 UTC

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/dashboard-slow-to-load/84993.md?page=1)