I apologize is this is a common question but search didn’t bring up much. I have a dashboard I use for my holiday light show every year. Historically, it’s just been a pretty boring vertically stacked dashboard built with grids but, of course, I want the shiny new toy so, this year, I rebuilt it with Sections (admittedly, it’s still pretty boring 
).
I’m finding the new Sections based dashboard frequently goes unresponsive, to the point that I can’t even click entities, let alone edit one of the Sections or individual items within a section. Looking at Task Manager, I can see that the Sections tab is using a decent amount of processor/memory. If I load the old dashboard, I see proc/mem at 1-2% and 400MB. If I switch to the Sections based board, I see proc/mem jump immediately to 5% and 600MB or so. If I click the main Edit button, it jumps to 7-8% and 1GB or so. If I leave it sitting in Edit mode, the memory just keeps climbing. Not sure if there is a leak or if it’s just something running in the background. These are all just to load the page, not to actually interact with it. My machine has plenty of horsepower so I’m not worried about the numbers specifically, just that they seem to be what’s affecting usability.
Anyway, long story short, are there known limitations to the Sections pages? Do more ‘Sections’ cause the page to have issues? I currently have about 25 sections on the page. Some are blank at the moment but most have 8 or so entity buttons (some with visibility filters) and 2-3 Uptime graphs (based on HA Ping entities).
I thought about breaking it into separate pages on the dashboard but pretty sure the dash is all loaded together. I’m just wondering if I’m asking too much of the design or if there’s something I can do to make this work. Side note, in the time it took me to write the few sentences above, the page is now at 2GB of memory and, even after disabling Edit mode, the memory continues to climb (usually to 4GB or so).
