Open chlebowa opened 4 months ago
As evidenced by #1236, the creating the filter panel (FilteredData
objects) is not the main culprit. Placing progress bars within filter panel ui or server functions did not yield additional information.
Tip to the assignee:
Moment when the FilteredData
is created for the module should be postponed in the same way as the data-filtering. Creation of FIlteredData should be conditional on:
An app built with the following
data
andmodules
(no filters) takes over a minute to start*, up to a minute and a half withmodule_specific = TRUE
. The data is not particularly large but larger than the typical example data used in NEST packages. Pre-processing takes about 10 seconds. Since modules do not start until viewed, the (near) entirety of app startup taken up byteal
itself. I suppose building the filter panel is one of the more time-consuming steps.*) Measuring in a fresh session, from runnig the script that attaches all necessary packages, creates data and modules, and runs the app, until the moment the notification
Data loaded - App fully started up
appears on screen.My question is: at what point should one consider the app taking too long to start? Is there a way to improve startup time?
10 datasets of ~30 MB in total and 13 modules
``` > data ✅︎ verified teal_data objectTagging @gogonzo for visibility.
Code of Conduct
Contribution Guidelines
Security Policy