# Slow GUI -- Browser

**URL:** <https://discourse.nodered.org/t/slow-gui-browser/34328>\
**Category:** General\
**Created:** [16 October 2020 02:19 UTC](https://discourse.nodered.org/t/slow-gui-browser/34328 "2020-10-16T02:19:05Z")\
**Posts on this page:** 1\
**Showing post:** 32

<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:** [26 November 2020 15:01 UTC](https://discourse.nodered.org/t/slow-gui-browser/34328/32 "2020-11-26T15:01:12Z")

</div>

> [@zenofmud](#):
>
> I can tell you right now, no body is going to try to figure out what your flow is doing

I did 😛

Its huuuuuugggggeeeee & while I didnt see the 20sec freezes like the OP (on a i7 PC with 16GB RAM) I it was definitely sluggish (2 / 3 sec delays) so i suspect a lesser machine would struggle.

there are certainly areas that could be improved (like several places a switch node with 10+ outputs and its following nodes could all be simplified into one function & a switch statement) but i kinda suspect its just down the these shear volume of nodes and wires in one instance.

If you can break these down somewhat, distribute them across multiple machines (probably even [separate instances](https://discourse.nodered.org/t/node-red-multiple-instances/9787/7) on the same server would help) then start there. Use MQTT to coordinate the signals where things interact.

  

> [@zenofmud](#):
>
> I would suggest disabling tabs till you isolate the issue

I suspect its down to the shear qty of nodes so disabling tabs may not help (as they are still present in the flow & in the editor)

---

_[View the full topic](https://discourse.nodered.org/t/slow-gui-browser/34328)._