Open MarcSkovMadsen opened 1 year ago
I would recommend using functools.cache
or something similar and then cache the 64 latest conversions or similar.
Reasonable suggestion but I think we're going to move to client-side markdown rendering anyway.
It seems we will not be moving to client side rendering. We just switched to market-it-py on server side.
Not right away anyway, in the long run we may very well do so.
Just pushed a small change into https://github.com/holoviz/panel/pull/4693 that will cache the markdown renderer. Seeing a 2-3x rendering performance improvement over the old markdown renderer.
I'm working on #4281
I can see that for a static Markdown document ~15% of the launch time is spent on converting the Markdown. As the Markdown is static it should be possible to just convert this once and for all.
I see users of data apps being very happy about using Markdown to add documentation, navigation, images and videos to their apps. But the Markdown is normally static. Thus not caching the converted Markdown is a big overhead.
Reproduce
open /home 10 times open /admin