when opening the app page, it sometimes takes ~5 seconds for anything to appear. it then often takes ~5 seconds for the interactive components to appear. other than being annoying, users may think something is wrong
some of this might be unavoidable limitations of this being a marimo WebAssembly notebook, but there may be ways to shorten or at least warn about these loading times
I think there are a couple of things contributing to the loading times:
- general startup time
- installing python packages
- long-running notebook cells
using parquet files instead of csvs may help
adding conditional logic or marimo lazy loading for expensive cells like python package instillation or loading csv files may help (e.g. a button for a user to press and then wait for things to load)
a minimal landing to prompt users to "start the app" may give them a a quick initial interaction and make the app loading time expected/tolerable/less confusing
when opening the app page, it sometimes takes ~5 seconds for anything to appear. it then often takes ~5 seconds for the interactive components to appear. other than being annoying, users may think something is wrong
some of this might be unavoidable limitations of this being a marimo WebAssembly notebook, but there may be ways to shorten or at least warn about these loading times
I think there are a couple of things contributing to the loading times:
using parquet files instead of csvs may help
adding conditional logic or marimo lazy loading for expensive cells like python package instillation or loading csv files may help (e.g. a button for a user to press and then wait for things to load)
a minimal landing to prompt users to "start the app" may give them a a quick initial interaction and make the app loading time expected/tolerable/less confusing