Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mkdocs build is very slow (jupyter notebooks re-rendering even when no changes) #545

Open
mfisher87 opened this issue Apr 26, 2024 · 3 comments
Labels
documentation Improvements or additions to documentation

Comments

@mfisher87
Copy link
Member

mfisher87 commented Apr 26, 2024

Mkdocs currently lacks caching features we would need to fix this: danielfrg/mkdocs-jupyter#161

@mfisher87 mfisher87 added the documentation Improvements or additions to documentation label Apr 26, 2024
@mfisher87 mfisher87 changed the title Mkdocs build is very slow Mkdocs build is very slow (jupyter notebooks re-rendering even when no changes) Apr 26, 2024
@betolink
Copy link
Member

This would be nice indeed! maybe we can contribute upstream? Just a note that this is mostly for when we are working on a single notebook, for the whole documentation I think we can pass --dirtyreload to mkdocs to avoid re-executing the whole site. mkdocs/mkdocs#1074

@mfisher87
Copy link
Member Author

Readthedocs builds still wouldn't benefit, right?

I feel like upstreaming something like Quarto's "freeze" feature might not be too heavy a lift. Our builds right now are pretty wasteful, and it would be the right thing to do.

@betolink
Copy link
Member

Correct, I don't think readthedocs has a partial build workflow, the hope is that if context is persisted between builds maybe jupyter-cache can speed things up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants