Best Practices for Caching Marimo Reports?
We run an internal reporting application that I would like to speed up significantly. The flow of these reports are all pretty simple:
1. Pull Data
2. Run a bunch of calculations
3. Build visualizations
4. Display
What I think Marimo is probably capable of, but it isn't super clear to me yet? Is doing something like where we cache the report once it has been calculated. And if the same report is calculated again, just pull in the html that was previously cached. If it is the first time, build the full report and cache that html.
Are there any examples around this? What feels weird to me is a notebook caching itself as html programatically and potentially displaying a cached version of itself. But it seems like the tools are probably already in place to do this?
0 Replies