Improve dashboard (rows) performance

[leepeuker]

Currently when loading the dashboard we are fetching the data for all possible dashboard rows regardless of which rows are really shown in the frontend.

• [ ] only fetch the data for visible rows
• [ ] create endpoint to fetch rendered html dashboard rows
• [ ] fech the html for all rows asynchronous on dashboard page load
• [ ] prioritize the extended rows html loading

Loading all rows immediately improves loading times during dashboard usage

[JVT038]

Would this mean that the dashboard row data would only be loaded when the user unfolds / extends the row?

[leepeuker]

Yeah good question. I was thinking to still keep it in the backend, so only to remove the data for the rows wich are not rendered.

We could move the data fetching into js frontend, but that would mean we have to render the html in the frontend too. This would probably the the best thing to do, but requires the most change effort.

[JVT038]

It shouldn't be that difficult right?

Just add an event listener to check whether the user has extended the rows and if yes, add a loading spinner and make a POST request in the background to the backend, to fetch the data. When the data has arrived, remove the spinner and manipulate the DOM to inject the requested data.

[leepeuker]

I did not say that it is difficult, but it takes time