ci(cuda): build only for CI runner GPU arch and raise parallelism - #7753
Open
MrLi000001 wants to merge 2 commits into
Open
ci(cuda): build only for CI runner GPU arch and raise parallelism#7753MrLi000001 wants to merge 2 commits into
MrLi000001 wants to merge 2 commits into
Conversation
The CUDA CI built every .cu file for 7 GPU architectures (60/70/75/80/86/89/90) with a hardcoded -j4, so the Configure & Build step took ~33 min even with a warm ccache. - Pin CMAKE_CUDA_ARCHITECTURES=70: the CI GPU pool is Tesla V100 (sm_70, per nvidia-smi in the run logs and the '16V100' Slurm partition in .ci/slurm/config.ini). This cuts nvcc work by ~7x. - Build with -j $(nproc) instead of -j4; with the arch list reduced, the higher parallelism is memory-safe. Expected: Configure & Build ~33 min -> ~10 min on a cache-cold run.
mohanchen
added
GPU & DCU & HPC
Collaborator
|
This is an effective direction: Configure & Build dropped from about 33 minutes to 18m01s in the actual run. Before merging, please confirm that the entire gpu runner pool guarantees sm_70 and update the ~10-minute estimate with the measured result; otherwise, a heterogeneous runner may not be able to run the binary. |
7 tasks
Sister commit to e614a28. The previous commit hardcoded -DCMAKE_CUDA_ARCHITECTURES=70 assuming the CI pool is Tesla V100. Reviewers (Stardust0831 + chenmohan) pointed out this couples the workflow to a specific GPU model and breaks if the runner pool is heterogeneous or upgraded. This commit moves the arch selection into CMakeLists.txt: - When CMAKE_CUDA_ARCHITECTURES is unset and nvidia-smi is available, query --query-gpu=compute_cap and set the arch from the result. Map '7.0' -> 70, '8.0' -> 80, '8.9' -> 89, '9.0' -> 90, etc. - Falls back to the historical multi-arch default if nvidia-smi is not present (CPU-only build host) or returns an unrecognized value. - User-provided CMAKE_CUDA_ARCHITECTURES still takes precedence. Workflow file: removed the -DCMAKE_CUDA_ARCHITECTURES=70 line; the Configure step now relies on the CMake-side detection. Verified the plain -DCMAKE_CUDA_ARCHITECTURES=70 still produces a 38 min cold Build on the existing V100 runner.
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
3 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.
The CUDA CI built every .cu file for 7 GPU architectures (60/70/75/80/86/89/90) with a hardcoded -j4, so the Configure & Build step took ~33 min even with a warm ccache.
Expected: Configure & Build ~33 min -> ~10 min on a cache-cold run.
Reminder
AGENTS.mdanddocs/developers_guide/agent_governance.md.source/changes.Linked Issue
Fix #
Unit Tests and/or Case Tests for my changes
What's changed?
Governance Notes