Responsiveness & Speed & HA Slowdown

[lightingman117]

Not trying to detract or diminish the magnitude of an accomplishment this is.
Also, I understand the underlying hardware is quite low-power.
I am not in any way complaining or wanting more.
I am happy with what it can do and what I paid for it (free, though I plan to donate).

I've noticed many things seem a bit sluggish at times and sometimes do not respond.
Is this to be expected? [If so, no worries I'll accept the limitations]
I just want to check my setup.

Environment:
HA on Unraid server as a VM, I gave it 16 P-cores and 16G ram on a 13900K, so should have plenty of horsepower... (I wanted ESPHome compiling fast)
I have 2k entities, 173 devices

ESPHome 2025.5.2
Version Blueprint 4.3.15
Version ESPHome 4.3.15
Version TFT 4.3.15

Things I've noticed:

• HA overall is a bit more sluggish
• HA main GUI page sometimes refreshes and takes a long time (along with other pages)
• HA automation GUI for NSPanel is very sluggish (was not at first load, but now it is)
• Blueprint automation takes forever to load entities
• NSPanel swipe page does not always work (swiping to wake up and holding down for utilities or weather or climate does work 100%).

Things I have not noticed:

• Any glitches with uploads
• Any glitches with the blueprint updating the NSPanel
• Any glitches with the NSPanel connectivity or entity updates (refreshes are nearly instant)

[edwardtfn]

There are some conditions that could overload the logic and the most common is having in the home page some sensor with a high update rate.
The automation itself (Blueprint) is quite big (>10000 lines of code), so every run costs. And it will triggered every time any HA element associated changes.
There are some protections, like when the component triggering does not belongs to the currently visible page, then the automation will stop even before registering it's execution in the Logbook (or any event), however the element in the home page are an exception to this (those are sent to the panel even when that page is not visible, unless set in the specific settings in the Blueprint).
I have see in some cases where users tried to assign to the home page a template power sensor which is a sum of all their power sensor. As power changes quite dynamically and the template sensor will have a new value every time any of the other sensors changes, then you can have even more than an update per second. This will trigger the automation every second to send the new info to the panel, consuming CPU, network, etc.