Document -j auto in Building the manual
#7474
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Calinou
added
enhancement
cherrypick:3.5
cherrypick:3.6
area:manual
mhilbrunner
approved these changes
Jun 6, 2023
Member
|
Thanks! |
mhilbrunner
added a commit
to mhilbrunner/godot-docs
that referenced
this pull request
Aug 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was considering defaulting to
-j2or even-j3, but Windows systems with 8 GB of RAM would likely struggle with this.In the meantime, it's worth documenting Sphinx's
-j autofor people with lots of RAM. On a system with 32 threads, a full cleanmake htmlbuild can peak to more than 20 GB of RAM for Sphinx itself:With
-j autoon an Intel Core i9-13900K, the documentation builds in 1m16s, whereas-j4requires 4m15s.