# Slow dashboard performance across machines

**URL:** <https://discourse.nodered.org/t/slow-dashboard-performance-across-machines/79884>\
**Category:** General\
**Tags:** node-red-dashboard\
**Created:** [17 July 2023 13:21 UTC](https://discourse.nodered.org/t/slow-dashboard-performance-across-machines/79884 "2023-07-17T13:21:41Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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:** [17 July 2023 19:57 UTC](https://discourse.nodered.org/t/slow-dashboard-performance-across-machines/79884/9 "2023-07-17T19:57:28Z")

</div>

The hardest part is getting your head around InfluxDB and configuring some sensible data. I know I posted some guidance on that quite a long time ago. You do also need to keep your InfluxDB databases to sensible sizes as well, especially on a Pi.

[How to effectively use InfluxDB - FAQs - Node-RED Forum (nodered.org)](https://discourse.nodered.org/t/how-to-effectively-use-influxdb/36885/5)

But InfluxDB has some built in features for trimming DB's but also for aggregating data. For example, I keep my once-per-minute sensor data for a week but also aggregate to hourly data as I go along and keep the hourly data (with min/max/avg data points) for a few years. InfluxDB has features for automating all of that.

---

_[View the full topic](https://discourse.nodered.org/t/slow-dashboard-performance-across-machines/79884)._