hi there, I am gaining my first experiences with Node Red with a deployment on a Raspberry Pi 3B.
My test flows work fine when accessing the dashboard / gui from other stations (e.g. Laptop with Chrome browser).
For (emergency) remote access however, I also have VNC running on that Raspberry Pi. This is to access and control not only the "local" Node Red installation but also my home automation controller located in the same network.
When I access the UI for the homematic (RaspberryMatic) device, all seems ok. After a short CPU peak to about 10%, it returns to "doing nothing" ~ 2-3% load.
However, when I access the local Node Red Dashboard / UI, the cpu load climbs very quickly to a steady 60+ % load and stays at that level for as long as I was monitoring it. On that pi I am currently using the default installed Chromium browser. As mentioned before, when accessing that pi from a remote networked computer, the CPU load is basically NOT impacted.
I now also tried accessing the Node-Red instance on the homematic raspberry pi (RaspberryMatic with RedMatic to be precise) and similar, the CPU load goes to about 33% and stays there. So, not as bad as visualising the local instance but still considerable load!
So, that leads me to my question - how can this be fixed?
Will a different browser work "better"? Is there an issue with showing the dashboard / UI on a local node? Can the "load" be influenced by controlling refresh rates or similar (if so how / where)?