Hi there,
since I changed some gauges into a raster tile, both browser (Firefox & Ubuntu) and APP (Android) are extremly slow and with a high CPU losd.
I am not sure if the raster tile or the graph (updated every second for a 1-hor power chart, 5 sources) is slowing the system down, but it has become terribly slow.
You can make trigger template sensors that mirror the values you need on your dash and sample those at a much slower rate. (make the trigger for the template something like once per minute or once per n sec.) The dash controls will update when the underlying data changes. Side benefits - they will survive restart and your dash controls wonât be âunknownâ during startup.
Right now youâre saturating the hell out of your front end and paying the price.
CPU load is 0,02.
It looks like the Shelly pro3EM-integration does this frequent update interval on its own. Could be an indicator that too many of those fast-pushing / polling devices could tend to a GUI overload, when displayed as a chart.
Might be worth a feature for charts to âflatten / smoothenâ them internally before handing them over for display.
The machine itself has no limits, as itâs on a 40-core / 128GB VM. Currently assigned are 4 cores and 8GB RAM.
Update: I switched over to ApexCharts, great improvement. Thanks for all the hints!