WIP: compute-matrix: add 'docs-build' matrix, switch docs builds to RTX Pro 6000 - #627
Draft
jameslamb wants to merge 2 commits into
Draft
WIP: compute-matrix: add 'docs-build' matrix, switch docs builds to RTX Pro 6000#627jameslamb wants to merge 2 commits into
jameslamb wants to merge 2 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Introduces a
docs-buildmatrix to thecompute-matrixjob, so we can centrally control which runner types are used for docs builds.Details
RAPIDS projects generally need a GPU in their docs builds because things like Sphinx
autosummaryrequire actuallyimport-ing the libraries, and many of the libraries require a GPU at runtime.Today, projects are using the
custom-jobshared workflow and hard coding a GPU type, mostly L4.(example from NVIDIA/cuml)
L4 runners are heavily used in the shared CI runner system we use right now, which can result in long queue lines:
Look how often they've been 100% utilized in the last 2 days:
We'd like to switch to a less-busy runner type, such as RTX Pro 6000:
Centralizing that choice of runner type would mean that changing it in the future wouldn't require PRs like NVIDIA/cudf#23878 in every repo. I think that's justified here... it's really unlikely that docs builds would be sensitive to the particular details of a runner, as long as it's a GPU RAPIDS supports.