Dashboard browser memory / strain vs. number of views

Hi there,

I have quite a large dashboard with a view for each room / device

Recently my tablet in my kitchen which is running fully kiosk on Android has startet to become unresponsive while displaying my default dashboard. I changed some settings in fully kiosk and moved a selected part of my views to a new Dashboard which I then display instead. Since then the tablet has been stable.

Will a browser load all views of a Dashboard even though it is only displaying one view, or should it not make a difference ressource wise on the browser displaying the dashboard?

1 Like

I’m keen to understand this too. I have two tablets that seem to be struggling with performance. I think it’s due to having too many dashboards that each have several views.

So I have decided to rationalise and reduce the number of dashboards.

I’m part way through creating two dashboards (one for each tablet) with each one having only one default (home) view.

I have another dashboard with several views used for areas/rooms etc. The intention is to have each tablet access those views, therefore cutting down duplication.

I’ll report back to see if I notice a difference in browser performance once I’ve finished.