Currently the llms.txt builder is triggered when the main build finishes. This effectively starts a whole second build using the sphinx-markdown-builder which can double the build times.
https://github.com/jacobtomlinson/sphinx-llm/blob/1a84a18f1cff431bcf3c5f39c08198bba4d0b108/src/sphinx_llm/txt.py#L29
To improve performance we could trigger the build in a separate process at the start of the primary build so that it runs in parallel. Then consolidate the files into one structure as a post-build step.
Depending on performance differences between the html/dirhtml builder and the markdown builder the overall build time would be whichever of the two is slower, plus some small reconciliation overhead.
Currently the
llms.txtbuilder is triggered when the main build finishes. This effectively starts a whole second build using thesphinx-markdown-builderwhich can double the build times.https://github.com/jacobtomlinson/sphinx-llm/blob/1a84a18f1cff431bcf3c5f39c08198bba4d0b108/src/sphinx_llm/txt.py#L29
To improve performance we could trigger the build in a separate process at the start of the primary build so that it runs in parallel. Then consolidate the files into one structure as a post-build step.
Depending on performance differences between the html/dirhtml builder and the markdown builder the overall build time would be whichever of the two is slower, plus some small reconciliation overhead.