NCCL Topology Detection Regression (v2.18.3+)
NCCL v2.18.3 introduced a topology detection regression that misidentifies GPU-NIC affinity on some systems, causing NCCL to use a suboptimal communication path. Denpex detects the regression from NCCL version and topology logs.
NCCL v2.
What this failure is
NCCL Topology Detection Regression (v2.18.3+) is a Communication failure seen during ML training runs. NCCL v2.18.3 introduced a topology detection regression that misidentifies GPU-NIC affinity on some systems, causing NCCL to use a suboptimal communication path. Denpex detects the regression from NCCL version and topology logs. Common tags: Nccl, Topology, Regression, Version.
Is this what broke your run? Paste your log.
You're reading about NCCL Topology Detection Regression (v2.18.3+). Paste your own crash log or traceback below and get the real root cause for YOUR run, not this generic entry. No account, no card. Logs are masked at ingress and never saved to account history.
Want 14 days on the Scale plan?
Request an evaluation code. A verified workplace organization activates up to 50 diagnoses a day, alerts, history, and follow-up questions. No credit card or automatic subscription.
Why it happens (the mechanism)
NCCL v2.18.3 changed the topology detection algorithm to handle more complex NIC configurations, but the new algorithm produces incorrect GPU-NIC affinity on some systems. The regression causes NCCL to assign GPUs to NICs across NUMA boundaries instead of within the same NUMA node. On systems with NVSwitch, the regression may incorrectly prefer P2P transport over the faster NVLS transport. The fix was included in NCCL v2.22.x but not backported to v2.18.x or v2.19.x. Taken together, these mechanisms explain why the failure is reproducible, why it tends to surface on specific workloads or scales, and why generic mitigation attempts often fall short without addressing the underlying cause.
What you'll observe
- Training performance degrades after upgrading NCCL to v2.18.3 or later
- NCCL uses a different (worse) topology than the previous version
- GPU-NIC affinity is incorrect in the NCCL topology XML after the upgrade
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| NCCL topology XML shows different GPU-NIC assignments after upgrading NCCL | NCCL v2.18.3 changed the topology detection algorithm to handle more complex NIC configurations, but the new algorithm produces incorrect GPU-NIC affinity on some systems |
| Performance regression of 10-50% on multi-node training after NCCL upgrade | The regression causes NCCL to assign GPUs to NICs across NUMA boundaries instead of within the same NUMA node |
| NCCL_DEBUG=INFO shows different channel counts or algorithm selections than before | On systems with NVSwitch, the regression may incorrectly prefer P2P transport over the faster NVLS transport |
| Downgrading NCCL to v2.18.1 restores performance | The fix was included in NCCL v2.22.x but not backported to v2.18.x or v2.19.x |
Which systems are affected
- Multi-node GPU training with NCCL v2.18.3 through v2.21.x
- Systems with multiple NICs per node where topology detection is critical
- Heterogeneous GPU-NIC configurations
- Clusters that upgraded NCCL for a security fix but got a performance regression
How to confirm this is the problem
Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.
- ✓Reproduce the failure from a clean checkpoint/seed: the symptom must appear without warm-up state from a previous run.
- ✓Verified signal present: NCCL topology XML shows different GPU-NIC assignments after upgrading NCCL
- ✓Verified signal present: Performance regression of 10-50% on multi-node training after NCCL upgrade
- ✓Verified signal present: NCCL_DEBUG=INFO shows different channel counts or algorithm selections than before
- ✓Verified signal present: Downgrading NCCL to v2.18.1 restores performance
- ✓A targeted fix from the "How to fix it" section eliminates or substantially reduces the symptom within one validation pass.
The fix and the prevention pattern
The root cause is on this page and stays free. A free account adds the exact remediation steps, saved history, and the fix on every entry in the encyclopedia.
Sign up free. Unlock the full analysisNo credit card. Daily allowance follows verified trust tier. Instant access.
Diagnose this failure in VS Code
Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.
Install the free VS Code extensionNCCL errors in context
NCCL is where a distributed job reports failure, which is not the same as where it failed. The hub lists every common NCCL error next to what it actually indicates, and the environment variables that tell them apart.
Compare every nccl error side by sideRelated failures to investigate next
Root cause
- NCCL v2.18.3 changed the topology detection algorithm to handle more complex NIC configurations, but the new algorithm produces incorrect GPU-NIC affinity on some systems
- The regression causes NCCL to assign GPUs to NICs across NUMA boundaries instead of within the same NUMA node
- On systems with NVSwitch, the regression may incorrectly prefer P2P transport over the faster NVLS transport
- The fix was included in NCCL v2.22.x but not backported to v2.18.x or v2.19.x
The fix and how to prevent it
Evaluate Denpex on your own logs
Request a Scale evaluation code. A verified workplace organization activates 14 days with up to 50 diagnoses a day. Every account keeps its current diagnosis allowance and gets a verification path. No card or automatic subscription.
Don't just read the fix, diagnose your run
The encyclopedia tells you what went wrong. Denpex tells you what went wrong in YOUR training run. With your logs, your config, and your stack.