Repository navigation
Conversation
One row for 2 nodes x 16 ranks, AllGather [144M, 224M): Ring/Simple with 48 channels instead of the default 64. It runs 6% to 14% faster there in float, bfloat16 and half. All other rows are unchanged. Co-Authored-By: Claude <noreply@anthropic.com>
✅ All Policy Checks Passed
📖 Need help? See the Policy FAQ for details on every check and how to fix failures. |
Contributor
pr-rocm-systems-14858-oci-rccl-pr-smokeBuilds
FailuresNo failing tests in this run. 15 tests skipped. |
Contributor
pr-rocm-systems-14858-ruby64-rccl-pr-smokeBuilds
FailuresNo failing tests in this run. 15 tests skipped. |
aduforest
added a commit
that referenced
this pull request
Nov 3, 2026
1 task done
Member
Author
|
Folded into #14722, which now contains the combined two-node tuning and boundary/fallback tests. The original benchmark evidence and limitations are preserved and linked there. Closing this PR as superseded; no changes were merged into develop. |
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.
Motivation
Improve AllGather performance on MI350X, 2 nodes × 8 GPUs (16 ranks). Using 48 instead of 64 channels reduces time by 6.8%-13.5% in the samples below.
Technical Details
Adds this row to
projects/rccl/tuner/rccl_tuner_gfx950.csv:Uses Ring/Simple with 48 channels for
144 MiB <= size < 224 MiB, only on two nodes with 16 ranks. Exactly 224 MiB and settings outside this scope are unchanged.Test Plan
Reported rccl-tests coverage: six rounds comparing existing/new settings with repeated controls, sizes around the changed range and a wider 1-512 MiB sweep. Coverage includes float/bfloat16/half, CTA policies, registration modes and graph/non-graph runs; it does not establish every combination was tested. Correctness checking was enabled (
-c 1).Test Result
Measurements and command template
Representative timings, Ring/Simple with 64 channels before and 48 after:
The last sample is 256 bytes below 224 MiB.
RCCL develop, 16 ranks (one per GPU). Select one value per placeholder and add
-G 1for graphs:For the wider sweep, replace the size arguments with
-b 1M -e 512M -f 2. These are templates, not a complete run transcript.Previously investigated shared CI issues: GPU visibility in the test runner (#14944) and the policy bot's missing required check (#11156).
Issue Tracking
JIRA ID: AICOMRCCL-3447
Submission Checklist