# \[Reference\] Optimising Node-RED

**URL:** <https://discourse.nodered.org/t/reference-optimising-node-red/38321>\
**Category:** General\
**Created:** [31 December 2020 12:32 UTC](https://discourse.nodered.org/t/reference-optimising-node-red/38321 "2020-12-31T12:32:08Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![mudwalker](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mudwalker](https://discourse.nodered.org/u/mudwalker)\
**Post date:** [31 December 2020 17:15 UTC](https://discourse.nodered.org/t/reference-optimising-node-red/38321/6 "2020-12-31T17:15:12Z")

</div>

Excellent thread.

I must admit, I did start out trying to keep everything optimised on the Pi 3B+, was this way of doing it faster than that, etc.. But later realised that it was Stability over anything else I was after.

As for speed, in my application - using Node-RED as a communication hub, data logger and HMI for a Home Control system running on a separate controller, time is not of the essence, what does in matter if I don't read a temperature for another second?

However, I shall watch this thread with interest to see if I can add some of the stuff to my flows!

---

_[View the full topic](https://discourse.nodered.org/t/reference-optimising-node-red/38321)._