You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently myst build --execute runs executable content asynchronously. However, when notebooks depend on one another, achieving synchronous execution requires hacky solutions, such as making one notebook wait for a specific file created by another.
Also, simultaneous execution can cause issues when multiple resource-intensive notebooks are included, mostly performance bottlenecks.
Would it be possible to introduce a feature in myst.yml to specify the execution order of notebooks? Incorporating memory flushing between notebook executions could greatly enhance efficiency and resource management.
Thank you!
The text was updated successfully, but these errors were encountered:
Proposal
Currently
myst build --execute
runs executable content asynchronously. However, when notebooks depend on one another, achieving synchronous execution requires hacky solutions, such as making one notebook wait for a specific file created by another.Also, simultaneous execution can cause issues when multiple resource-intensive notebooks are included, mostly performance bottlenecks.
Would it be possible to introduce a feature in
myst.yml
to specify the execution order of notebooks? Incorporating memory flushing between notebook executions could greatly enhance efficiency and resource management.Thank you!
The text was updated successfully, but these errors were encountered: