📝 官方博客NVIDIA Developer BlogCodex · 实盘不做把握 3/10不做原因:证据不足
北京时间·🕒 发布 23:08:39(美西 08:08)·⟳ 抓取 23:09:05 +26s·⚡ 决策 08-24 23:17:15 +8m10s·63.6 天前
英伟达发布Spectrum-X Ethernet技术博客,强化AI工厂网络架构叙事但无新增商业订单
本次博客强化NVIDIA AI网络技术叙事,但没有新增客户、订单、金额、收入指引或可量化商业化节点;对NVDA.US做多和对ANET.US做空都缺少足够预期差。
📄 原文NVIDIA Developer Blog↗ 原文
Giga-Scale AI and the Ethernet Evolution: How Spectrum-X Ethernet Rewrites the Rules
The massive growth of generative AI has fundamentally altered data center design. As distributed model training scales…
不做 英伟达(NVDA.US)
不做多:官方技术博客方向正面但无新增订单、客户、金额或指引,超大市值标的短线增量不足。
不做 CSOP NVIDIA Daily Max (2x) Leveraged Product(07788.HK)
不做多:2倍产品只放大NVDA方向,港股已收盘且底层事件无新增商业edge。
不做 CSOP NVIDIA Daily Max (2x) Leveraged Product(09788.HK)
不做多:USD计价2倍产品同样依赖NVDA正向重定价,本次催化不足。
不做 CSOP NVIDIA Daily Max (-2x) Inverse Product(07388.HK)
不做空:当前事件不是NVIDIA新增利空,反向产品无交易依据。
不做 CSOP NVIDIA Daily Max (-2x) Inverse Product(09388.HK)
不做空:USD计价反向产品需要NVDA明确负面催化,本次不满足。
不做 Arista Networks(ANET.US)
不做空:NVIDIA竞争叙事存在但本次不是新增客户替换或份额损害,强空催化不足。
展开详情(成交明细 / 研究档案 / 原文全文 / 决策记录链)
研究档案
结论摘要
Spectrum-X Ethernet是NVIDIA AI工厂网络的重要产品线,技术叙事长期利好NVIDIA并可能压制传统以太网设备商估值叙事;但这篇NVIDIA Developer Blog主要解释既有架构、性能和多平面设计,商业采用与产品路线此前已公开。本次新增事实不足以推动NVDA.US这种超大市值股票短线重定价,也不足以构成ANET.US的明确强空催化。
消息传播链
- NVIDIA官方开发者博客发布Spectrum-X Ethernet架构说明,属于一手技术内容但非法定披露。
- 旧背景:NVIDIA已宣布Spectrum-X采用、合作伙伴和性能提升,说明本次博客不是该商业主线首次披露。
- 旧背景:NVIDIA此前已披露Spectrum-X、MRC、多平面网络和OpenAI/Microsoft/Oracle相关叙事。
关键理由
- Spectrum-X Ethernet继续强化NVIDIA在AI数据中心网络的全栈叙事,但本文没有新增订单、客户或收入指引。
- Arista存在长期竞争传导,但做空需要新增客户迁移、份额损害或财务指引变化,本次博客达不到强空标准。
- 直接杠杆和反向产品只放大NVDA方向,不能解决底层事件缺少短线商业增量的问题。
主要风险
- 若随后NVIDIA或客户同步披露大额Spectrum-X订单、云厂商采用或收入节奏上调,NVDA.US与ANET.US判断需重评。
- 关系库覆盖状态标注为stale且fallback_required,但已列出的直接产品不改变本次edge不足结论;若出现未覆盖的可交易产品,也只会复制NVDA方向。
反向证据
- 做多前查反向 · 来源 web · 日期 2026-05-06 · 影响 weakens
OpenAI、Microsoft、Oracle和多平面网络叙事此前已公开,削弱本次作为NVDA新多头催化的增量。
检索:NVIDIA Spectrum-X Ethernet prior adoption OpenAI Microsoft Oracle 2026 原文 ↗ - 做多前查反向 · 来源 web · 日期 2024-06-02 · 影响 weakens
Spectrum-X采用和合作伙伴信息此前已有IR披露,本次博客没有新增采购承诺。
检索:NVIDIA Spectrum-X Ethernet adoption partners 2024 原文 ↗ - 做空前查反向 · 来源 web · 日期 2025-10-13 · 影响 weakens
历史上Arista对Spectrum-X客户采用消息会承压,但本次没有新增客户采用,做空催化不够强。
检索:Arista Networks stock falls NVIDIA Spectrum-X adoption Meta Oracle 原文 ↗
先例如何影响了这次决策
对本次决策的影响:先例降低了本次对技术博客直接交易的信心,确认应等待客户、订单、收入或指引类硬催化。
方向:低相似先例显示,Spectrum-X若伴随客户采用会利好NVIDIA并压制Arista;但纯技术博客的方向强度不足。
涨幅量级:没有8分以上同市场同机制先例,不能用历史样本校准tp/sl或支持ENTER。
形态:可见样本更像商业采用节点才有交易反应,技术叙事本身容易缺少新增量。
历史先例(按相似度)
- 相似度 5/10 ANET 2025-10-13 NVIDIA披露Meta和Oracle采用Spectrum-X后,Arista被市场解读为潜在受损方。 原文 ↗
事件后 +1日 -1.8% · +2日 -7.6% · +3日 -4.5% · +4日 -2.8% · +5日 -4.7%
⚠非首发(转载/聚合)·来源层级不符(声明media/实为aggregator) — 该行涨幅别用来定止盈止损
相似度依据:同为NVIDIA Spectrum-X相关信息对Arista竞争叙事的影响,但当时涉及Meta和Oracle采用,商业强度高于本次技术博客。
经验:客户采用型Spectrum-X新闻可压制Arista,但纯技术解释不应机械外推。 - 相似度 4/10 NVDA 2024-06-02 NVIDIA宣布Spectrum-X被云服务商和系统厂商采用,并公布产品节奏。 原文 ↗
事件后 +1日 +4.9% · +2日 +6.2% · +3日 +11.7% · +4日 +10.4% · +5日 +10.3%
相似度依据:同属Spectrum-X官方披露,但2024年新闻稿包含采用名单和发布节奏,显著强于本次技术博客。
经验:Spectrum-X商业节点需要客户、产品节奏或收入证据,单纯技术内容对NVDA短线弹性有限。 - 相似度 4/10 NVDA 2023-11-20 NVIDIA宣布Dell、HPE、Lenovo将集成Spectrum-X以太网技术。 原文 ↗
事件后 +1日 +2.2% · +2日 +1.3% · +3日 -1.2% · +4日 -3.1% · +5日 -2.1%
相似度依据:同属Spectrum-X官方商业化披露,但包含Dell、HPE、Lenovo集成计划,强于本次文章。
经验:真正可交易的Spectrum-X催化通常来自系统厂商集成、客户采用或发售节点,而非技术白皮书式解释。
原文全文
展开原文 · 15,590 字
The massive growth of generative AI has fundamentally altered data center design. As distributed model training scales to span hundreds of thousands of GPUs, the scale-out network connecting these nodes has emerged as a first-order performance bottleneck.
For decades, traditional off-the-shelf Ethernet has been the undisputed king of enterprise and cloud networking. It is cheap, standardized, and highly effective at handling general-purpose, high-entropy web traffic. However, when traditional Ethernet is forced to handle the massive, highly synchronized communication patterns required by AI architectures, it hits a physical wall.
To bridge this gap, NVIDIA introduced Spectrum-X Ethernet, a hardware-accelerated networking architecture designed from the ground up for giga-scale AI factories. Unlike traditional Ethernet, which relies on decades-old routing and congestion control paradigms, Spectrum-X Ethernet co-designs high-performance switches and host-side network interface cards (NICs) to deliver predictable low latency, high fabric utilization, and robust resilience under extreme load and stress.
This post explores the structural limitations that make traditional Ethernet ill-suited for AI workloads, deconstructs the unique architectural principles of Spectrum-X Ethernet, and explains how Spectrum-X Multiplane technology maximizes bisection bandwidth and accelerates Time-to-AI.
Standard data center traffic is high entropy; millions of small, independent flows travel in different directions. Equal-Cost Multi-Path (ECMP) routing uses static flow hashing to spread them across parallel paths, generally producing balanced utilization.
AI training traffic is low entropy. GPUs continuously synchronize through collectives such as All-Reduce, All-Gather, and All-to-All, creating relatively few, very large, synchronized flows. This exposes three limitations of traditional Ethernet:
- Hash collisions and stragglers: ECMP doesn’t account for real-time congestion, so large flows may collide on one link while others are underused. Because synchronous collectives finish only when their slowest flow completes, one congested path can delay the collective and leave many GPUs idle.
- Lossy versus lossless operation: Congestion can overflow switch buffers and trigger packet loss and retransmission, delays that significantly hurt AI performance. RoCEv2 deployments often use Priority Flow Control (PFC) to reduce loss, but pause frames can propagate congestion, create head-of-line blocking, and potentially stall the fabric.
- Slow congestion control: Protocols such as Data Center Quantized Congestion Notification (DCQCN) can be difficult to tune for synchronized AI bursts. Delayed or excessive reactions can cause buffer buildup, underutilization, and latency spikes.
- Near-Perfect Multi-Tenant Isolation: With traditional Ethernet, “noisy neighbor” traffic from one job can bleed into another, causing an All-to-All collective’s bandwidth to collapse by more than 80%. This isolation failure was demonstrated in a DeepSeek-V3 LLM training simulation. When running standalone, standard Ethernet achieved a training step time of 735 ms. However, when background “noise” traffic was introduced, standard Ethernet’s step times inflated to 1.18 seconds (a 1.6x slowdown). Spectrum-X Ethernet, by isolating congestion per plane and dynamically routing around hotspots, maintained a stable training step time of 668 ms under both standalone and heavily congested multi-tenant conditions representing virtually zero degradation.
At 800 gigabits per second (Gbps) and beyond, propagation delay remains fixed by the speed of light, but the bandwidth-delay product is massive. To avoid queue build-up and packet loss, a network fabric must react to congestion in real-time, at microsecond timescales.
Because software-based control paths can’t react within these tight windows, Spectrum-X Ethernet implements full hardware acceleration as a core structural requirement. The fundamental design principle of Spectrum-X Ethernet is the separation of hardware-accelerated control loops by scope, signal, and responsibility. By decomposing network control into three distinct, non-interfering loops, Spectrum-X Ethernet resolves congestion at its natural timescale without creating feedback loops that destabilize the fabric.
Unlike traditional Ethernet’s static, hash-based ECMP routing, Spectrum-X Ethernet switches implement per-packet Adaptive Routing (AR). Utilizing a quantized hardware approximation of the Join-Shortest-Queue (JSQ) algorithm, the switch samples the queue depth of every egress port in an ECMP group at sub-microsecond intervals. When a packet arrives, the switch dynamically steers it to the least-congested physical port. This stateless, flow-agnostic mechanism reacts within hundreds of nanoseconds to transient local imbalances, keeping switch queues small and preventing localized hotspots.
While AR equalizes path utilization within the fabric, it can’t resolve endpoint incast, a scenario where multiple senders simultaneously transmit data to a single receiver, saturating the receiver’s egress port. To handle this, Spectrum-X Ethernet implements an advanced, hardware-accelerated Congestion Control (CC) mechanism.
Crucially, Spectrum-X Ethernet co-designs the switch and SuperNIC response: the switch only generates Explicit Congestion Notification (ECN) marks when its adaptive routing capacity is completely exhausted and the queue continues to grow. Senders utilize precise RTT probes combined with ECN marks to adjust their sending rates at RTT timescales. This prevents the network from overreacting to short-lived micro-bursts (which AR easily balances) while providing a rapid, precise rate reduction when genuine, endpoint-level congestion occurs.
Operating at the host edge, the Plane Load Balancer (PLB) is a dedicated hardware engine inside the Spectrum-X Ethernet SuperNIC (such as the NVIDIA ConnectX). The PLB dynamically distributes packets across multiple network planes, using a combination of local queue feedback and end-to-end, per-plane congestion telemetry. This mechanism is discussed in depth below.
To scale an AI factory to hundreds of thousands of GPUs, traditional networking architectures require adding additional tiers (e.g., moving from a 2-tier to a 3-tier fat-tree topology). However, adding tiers is highly problematic: it adds latency, increases jitter, introduces load imbalance, and massively inflates the cost of optics, cabling, and power.
To solve the scaling challenge, modern AI data centers leverage a Multiplane Topology. Instead of building a single, massive, multi-tiered network fabric, a Multiplane Topology decomposes a single host’s massive network bandwidth (for example, 800 Gbps from an 8-lane ConnectX SuperNIC) into multiple lower-speed, physically independent network planes (for example, four separate 200 Gbps planes). Each plane is built as a highly efficient, shallow two-tier fat tree.
To connect the hosts to these planes, passive optical devices such as shuffle-boxes or trunk cables are utilized at the host edge. These devices route fibers from each multi-port NIC to all independent planes, exposing massive path diversity at the host edge while maintaining complete NIC-to-NIC reachability. This allows a simple two-tier topology to scale to over 128,000 endpoints, or up to 16 million endpoints with a three-tier topology, without introducing the latency and jitter bottlenecks of a traditional multi-tier fabric topology.
While a Multiplane Topology offers massive theoretical bandwidth, it is only effective if traffic is perfectly balanced across all planes. Some standard architectures attempt to solve this by oblivious spraying, where packets are distributed sequentially across all planes at the transport layer without any visibility into individual plane conditions.
This approach breaks down completely in the real world. At giga-scale, physical faults, optical connector degradation, and fiber link flaps are steady-state operating realities. If a single fiber link in Plane 2 degrades or flaps, the capacity of that plane drops. Because oblivious spraying is blind to this asymmetry, it continues to dump equal amounts of traffic onto the degraded plane. As a result, the entire network’s performance is bottlenecked by the slowest, degraded plane, and a single localized link flap’s blast radius is amplified to encompass the entire multiplane cluster.
To unlock the true potential of multiplane architectures, Spectrum-X Multiplane technology implements a hardware-accelerated Plane Load Balancer (PLB) directly in the SuperNIC silicon. The Plane Load Balancer makes the multiplane architecture completely transparent to the application layer; the operating system and the collective communication libraries see only a single, unified RoCE device. All traffic distribution, load balancing, and failure failover are handled entirely within the Spectrum-X Ethernet hardware.
In concert with the Spectrum-X Ethernet switch, the PLB operates via a unique, stateful, two-stage hierarchical selection process for every packet transmitted:
- End-to-End Congestion Filtering: For every destination GPU, the SuperNIC maintains independent, stateful Congestion Control contexts; one for each physical plane. Each context independently monitors RTT probes and processes Congestion Notification Packets (CNPs) to calculate the real-time rate allowance of its specific plane. Before a packet is sent, the SuperNIC compares the required transmission rate against the allowance of each plane. Any plane experiencing end-to-end congestion or link failure is temporarily filtered out of the eligible set.
- Local Queue Selection: From the remaining, healthy, uncongested planes, the SuperNIC hardware selects the plane with the shallowest local egress queue. This mirrors the switches’ Adaptive Routing mechanism at the host edge.
By separating CC state per plane and combining it with local egress queue depth, Spectrum-X Ethernet isolates congestion to the affected plane. If Plane 2 experiences a link failure, the Connect-X SuperNIC immediately detects the RTT timeout, masks Plane 2 from the eligible set, and transparently redirects all traffic across the remaining three healthy planes in under 3 milliseconds thus preserving 75% of the total line-rate bisection bandwidth.
To validate these architectural designs, NVIDIA and researchers have rigorously evaluated Spectrum-X Ethernet on production-grade clusters and high-fidelity simulations. The results demonstrate a stark contrast between Spectrum-X Ethernet and traditional, off-the-shelf Ethernet under high utilization, failure scenarios, and multi-tenant environments:
- Multiplane resiliency: For example, when a localized 20% switch-to-switch connectivity failure occurs on just one plane of an 8-plane network, a traditional Ethernet multiplane network immediately bottlenecks. Because it relies on oblivious load balancing, its performance across every single plane collapses to match the degraded plane, limiting the entire fabric to 80% capacity. In contrast, Spectrum-X Multiplane uses its stateful PLB to dynamically route around the localized bottleneck, keeping the seven healthy planes running at 100% capacity while only the degraded plane operates at 80%. By utilizing all available healthy capacity rather than sinking to the lowest common denominator, Spectrum-X Multiplane delivers a 1.2x higher overall All-to-All collective bandwidth during failures, providing the graceful, capacity-proportional degradation necessary to keep massive AI training jobs moving.
- Predictable high-utilization performance: Under a worst-case RDMA bisection benchmark, traditional Ethernet’s static ECMP routing collapses due to flow-hash collisions, with some GPU pairs experiencing throughput drops down to 25 Gbps. Spectrum-X Ethernet, utilizing AR and PLB, delivers a tight, predictable bandwidth distribution, sustaining 98% of the theoretical line rate across all GPU pairs. Furthermore, while traditional Ethernet exhibits wide latency jitter with a 99th percentile (P99) tail latency reaching 22 µs, Spectrum-X Ethernet maintains a low, tightly clustered P99 tail latency of just 8 to 9 µs under 75% network load.
- Seamless failover resiliency: When a link on a host-to-leaf connection flaps, traditional Ethernet’s software-based or non-accelerated load balancers require upwards of 1.08 seconds to recover and reroute traffic. This causes massive communication stalls that freeze GPU collective operations. In contrast, Spectrum-X Ethernet’s hardware-accelerated PLB detects the failure and completes the failover in just 2.68 milliseconds. This is a 400x speedup that absorbs transient failures transparently without disrupting ongoing LLM training steps.
A final consideration is that link failures are inevitable, but their performance impact should remain proportional to the loss of physical connectivity. Achieving this is difficult because multiple faults along a path can severely degrade connectivity for many source-destination pairs.
Traditional Ethernet degrades non-proportionally under cable faults and link flaps; dropping 10% of leaf uplinks can cause collective bandwidth to collapse by 50% or more due to routing asymmetry. Spectrum-X Ethernet degrades strictly capacity-proportionally. Under a 10% fabric link failure scenario, Spectrum-X Ethernet maintains near-ideal performance, with bandwidth degrading by a proportional 11% and tail latency increasing by a mere 7%.
This robust resiliency ensures that operators can run training workloads at near-optimal efficiency even before all physical infrastructure issues are fully resolved, drastically reducing “Time-to-AI”.
The transition from general-purpose cloud computing to giga-scale generative AI represents a fundamental shift in networking requirements. Traditional off-the-shelf Ethernet, built on the assumptions of high-entropy traffic, static routing, and software-controlled congestion loops, is fundamentally incapable of meeting the microsecond-scale, zero-jitter demands of synchronous AI collectives.
Spectrum-X Ethernet rewrites the networking rulebook. By decoupling and hardware-accelerating the key control loops with adaptive routing within the fabric, targeted congestion control at the transport layer, and PLB at the host edge, Spectrum-X Ethernet delivers the predictable, stable, and ultra-low-latency performance that giga-scale AI demands. Additionally, Spectrum-X Multiplane technology provides a robust, highly resilient, and operationally visible network fabric that simplifies cluster scaling, protects multi-tenant workloads, and minimizes “Time-to-AI”. For any organization building an AI factory, Spectrum-X Ethernet is not just a performance optimization—it is an architectural necessity.
To learn more about Spectrum-X Ethernet and Spectrum-X Multiplane, read the published whitepaper here.
- Khashab, S., et al. (2025). “High-Speed Networking for Giga-Scale AI Factories.” NVIDIA Technical White Paper
- Bai, W., et al. (2023). “Empowering Azure Storage with RDMA.” Proceedings of the USENIX Symposium on Networked Systems Design and Implementation (NSDI)
- Gangidi, A., et al. (2024). “RDMA over Ethernet for Distributed Training at Meta Scale.” Proceedings of the ACM SIGCOMM Conference
- DeepSeek-AI. (2024). “DeepSeek-V3 Technical Report.” arXiv preprint
- Khashab, S., et al. (2025). “NSX: Large-Scale Network Simulation on an AI Server” Proceedings of the ACM Conference on AI Networking
For decades, traditional off-the-shelf Ethernet has been the undisputed king of enterprise and cloud networking. It is cheap, standardized, and highly effective at handling general-purpose, high-entropy web traffic. However, when traditional Ethernet is forced to handle the massive, highly synchronized communication patterns required by AI architectures, it hits a physical wall.
To bridge this gap, NVIDIA introduced Spectrum-X Ethernet, a hardware-accelerated networking architecture designed from the ground up for giga-scale AI factories. Unlike traditional Ethernet, which relies on decades-old routing and congestion control paradigms, Spectrum-X Ethernet co-designs high-performance switches and host-side network interface cards (NICs) to deliver predictable low latency, high fabric utilization, and robust resilience under extreme load and stress.
This post explores the structural limitations that make traditional Ethernet ill-suited for AI workloads, deconstructs the unique architectural principles of Spectrum-X Ethernet, and explains how Spectrum-X Multiplane technology maximizes bisection bandwidth and accelerates Time-to-AI.
Standard data center traffic is high entropy; millions of small, independent flows travel in different directions. Equal-Cost Multi-Path (ECMP) routing uses static flow hashing to spread them across parallel paths, generally producing balanced utilization.
AI training traffic is low entropy. GPUs continuously synchronize through collectives such as All-Reduce, All-Gather, and All-to-All, creating relatively few, very large, synchronized flows. This exposes three limitations of traditional Ethernet:
- Hash collisions and stragglers: ECMP doesn’t account for real-time congestion, so large flows may collide on one link while others are underused. Because synchronous collectives finish only when their slowest flow completes, one congested path can delay the collective and leave many GPUs idle.
- Lossy versus lossless operation: Congestion can overflow switch buffers and trigger packet loss and retransmission, delays that significantly hurt AI performance. RoCEv2 deployments often use Priority Flow Control (PFC) to reduce loss, but pause frames can propagate congestion, create head-of-line blocking, and potentially stall the fabric.
- Slow congestion control: Protocols such as Data Center Quantized Congestion Notification (DCQCN) can be difficult to tune for synchronized AI bursts. Delayed or excessive reactions can cause buffer buildup, underutilization, and latency spikes.
- Near-Perfect Multi-Tenant Isolation: With traditional Ethernet, “noisy neighbor” traffic from one job can bleed into another, causing an All-to-All collective’s bandwidth to collapse by more than 80%. This isolation failure was demonstrated in a DeepSeek-V3 LLM training simulation. When running standalone, standard Ethernet achieved a training step time of 735 ms. However, when background “noise” traffic was introduced, standard Ethernet’s step times inflated to 1.18 seconds (a 1.6x slowdown). Spectrum-X Ethernet, by isolating congestion per plane and dynamically routing around hotspots, maintained a stable training step time of 668 ms under both standalone and heavily congested multi-tenant conditions representing virtually zero degradation.
At 800 gigabits per second (Gbps) and beyond, propagation delay remains fixed by the speed of light, but the bandwidth-delay product is massive. To avoid queue build-up and packet loss, a network fabric must react to congestion in real-time, at microsecond timescales.
Because software-based control paths can’t react within these tight windows, Spectrum-X Ethernet implements full hardware acceleration as a core structural requirement. The fundamental design principle of Spectrum-X Ethernet is the separation of hardware-accelerated control loops by scope, signal, and responsibility. By decomposing network control into three distinct, non-interfering loops, Spectrum-X Ethernet resolves congestion at its natural timescale without creating feedback loops that destabilize the fabric.
Unlike traditional Ethernet’s static, hash-based ECMP routing, Spectrum-X Ethernet switches implement per-packet Adaptive Routing (AR). Utilizing a quantized hardware approximation of the Join-Shortest-Queue (JSQ) algorithm, the switch samples the queue depth of every egress port in an ECMP group at sub-microsecond intervals. When a packet arrives, the switch dynamically steers it to the least-congested physical port. This stateless, flow-agnostic mechanism reacts within hundreds of nanoseconds to transient local imbalances, keeping switch queues small and preventing localized hotspots.
While AR equalizes path utilization within the fabric, it can’t resolve endpoint incast, a scenario where multiple senders simultaneously transmit data to a single receiver, saturating the receiver’s egress port. To handle this, Spectrum-X Ethernet implements an advanced, hardware-accelerated Congestion Control (CC) mechanism.
Crucially, Spectrum-X Ethernet co-designs the switch and SuperNIC response: the switch only generates Explicit Congestion Notification (ECN) marks when its adaptive routing capacity is completely exhausted and the queue continues to grow. Senders utilize precise RTT probes combined with ECN marks to adjust their sending rates at RTT timescales. This prevents the network from overreacting to short-lived micro-bursts (which AR easily balances) while providing a rapid, precise rate reduction when genuine, endpoint-level congestion occurs.
Operating at the host edge, the Plane Load Balancer (PLB) is a dedicated hardware engine inside the Spectrum-X Ethernet SuperNIC (such as the NVIDIA ConnectX). The PLB dynamically distributes packets across multiple network planes, using a combination of local queue feedback and end-to-end, per-plane congestion telemetry. This mechanism is discussed in depth below.
To scale an AI factory to hundreds of thousands of GPUs, traditional networking architectures require adding additional tiers (e.g., moving from a 2-tier to a 3-tier fat-tree topology). However, adding tiers is highly problematic: it adds latency, increases jitter, introduces load imbalance, and massively inflates the cost of optics, cabling, and power.
To solve the scaling challenge, modern AI data centers leverage a Multiplane Topology. Instead of building a single, massive, multi-tiered network fabric, a Multiplane Topology decomposes a single host’s massive network bandwidth (for example, 800 Gbps from an 8-lane ConnectX SuperNIC) into multiple lower-speed, physically independent network planes (for example, four separate 200 Gbps planes). Each plane is built as a highly efficient, shallow two-tier fat tree.
To connect the hosts to these planes, passive optical devices such as shuffle-boxes or trunk cables are utilized at the host edge. These devices route fibers from each multi-port NIC to all independent planes, exposing massive path diversity at the host edge while maintaining complete NIC-to-NIC reachability. This allows a simple two-tier topology to scale to over 128,000 endpoints, or up to 16 million endpoints with a three-tier topology, without introducing the latency and jitter bottlenecks of a traditional multi-tier fabric topology.
While a Multiplane Topology offers massive theoretical bandwidth, it is only effective if traffic is perfectly balanced across all planes. Some standard architectures attempt to solve this by oblivious spraying, where packets are distributed sequentially across all planes at the transport layer without any visibility into individual plane conditions.
This approach breaks down completely in the real world. At giga-scale, physical faults, optical connector degradation, and fiber link flaps are steady-state operating realities. If a single fiber link in Plane 2 degrades or flaps, the capacity of that plane drops. Because oblivious spraying is blind to this asymmetry, it continues to dump equal amounts of traffic onto the degraded plane. As a result, the entire network’s performance is bottlenecked by the slowest, degraded plane, and a single localized link flap’s blast radius is amplified to encompass the entire multiplane cluster.
To unlock the true potential of multiplane architectures, Spectrum-X Multiplane technology implements a hardware-accelerated Plane Load Balancer (PLB) directly in the SuperNIC silicon. The Plane Load Balancer makes the multiplane architecture completely transparent to the application layer; the operating system and the collective communication libraries see only a single, unified RoCE device. All traffic distribution, load balancing, and failure failover are handled entirely within the Spectrum-X Ethernet hardware.
In concert with the Spectrum-X Ethernet switch, the PLB operates via a unique, stateful, two-stage hierarchical selection process for every packet transmitted:
- End-to-End Congestion Filtering: For every destination GPU, the SuperNIC maintains independent, stateful Congestion Control contexts; one for each physical plane. Each context independently monitors RTT probes and processes Congestion Notification Packets (CNPs) to calculate the real-time rate allowance of its specific plane. Before a packet is sent, the SuperNIC compares the required transmission rate against the allowance of each plane. Any plane experiencing end-to-end congestion or link failure is temporarily filtered out of the eligible set.
- Local Queue Selection: From the remaining, healthy, uncongested planes, the SuperNIC hardware selects the plane with the shallowest local egress queue. This mirrors the switches’ Adaptive Routing mechanism at the host edge.
By separating CC state per plane and combining it with local egress queue depth, Spectrum-X Ethernet isolates congestion to the affected plane. If Plane 2 experiences a link failure, the Connect-X SuperNIC immediately detects the RTT timeout, masks Plane 2 from the eligible set, and transparently redirects all traffic across the remaining three healthy planes in under 3 milliseconds thus preserving 75% of the total line-rate bisection bandwidth.
To validate these architectural designs, NVIDIA and researchers have rigorously evaluated Spectrum-X Ethernet on production-grade clusters and high-fidelity simulations. The results demonstrate a stark contrast between Spectrum-X Ethernet and traditional, off-the-shelf Ethernet under high utilization, failure scenarios, and multi-tenant environments:
- Multiplane resiliency: For example, when a localized 20% switch-to-switch connectivity failure occurs on just one plane of an 8-plane network, a traditional Ethernet multiplane network immediately bottlenecks. Because it relies on oblivious load balancing, its performance across every single plane collapses to match the degraded plane, limiting the entire fabric to 80% capacity. In contrast, Spectrum-X Multiplane uses its stateful PLB to dynamically route around the localized bottleneck, keeping the seven healthy planes running at 100% capacity while only the degraded plane operates at 80%. By utilizing all available healthy capacity rather than sinking to the lowest common denominator, Spectrum-X Multiplane delivers a 1.2x higher overall All-to-All collective bandwidth during failures, providing the graceful, capacity-proportional degradation necessary to keep massive AI training jobs moving.
- Predictable high-utilization performance: Under a worst-case RDMA bisection benchmark, traditional Ethernet’s static ECMP routing collapses due to flow-hash collisions, with some GPU pairs experiencing throughput drops down to 25 Gbps. Spectrum-X Ethernet, utilizing AR and PLB, delivers a tight, predictable bandwidth distribution, sustaining 98% of the theoretical line rate across all GPU pairs. Furthermore, while traditional Ethernet exhibits wide latency jitter with a 99th percentile (P99) tail latency reaching 22 µs, Spectrum-X Ethernet maintains a low, tightly clustered P99 tail latency of just 8 to 9 µs under 75% network load.
- Seamless failover resiliency: When a link on a host-to-leaf connection flaps, traditional Ethernet’s software-based or non-accelerated load balancers require upwards of 1.08 seconds to recover and reroute traffic. This causes massive communication stalls that freeze GPU collective operations. In contrast, Spectrum-X Ethernet’s hardware-accelerated PLB detects the failure and completes the failover in just 2.68 milliseconds. This is a 400x speedup that absorbs transient failures transparently without disrupting ongoing LLM training steps.
A final consideration is that link failures are inevitable, but their performance impact should remain proportional to the loss of physical connectivity. Achieving this is difficult because multiple faults along a path can severely degrade connectivity for many source-destination pairs.
Traditional Ethernet degrades non-proportionally under cable faults and link flaps; dropping 10% of leaf uplinks can cause collective bandwidth to collapse by 50% or more due to routing asymmetry. Spectrum-X Ethernet degrades strictly capacity-proportionally. Under a 10% fabric link failure scenario, Spectrum-X Ethernet maintains near-ideal performance, with bandwidth degrading by a proportional 11% and tail latency increasing by a mere 7%.
This robust resiliency ensures that operators can run training workloads at near-optimal efficiency even before all physical infrastructure issues are fully resolved, drastically reducing “Time-to-AI”.
The transition from general-purpose cloud computing to giga-scale generative AI represents a fundamental shift in networking requirements. Traditional off-the-shelf Ethernet, built on the assumptions of high-entropy traffic, static routing, and software-controlled congestion loops, is fundamentally incapable of meeting the microsecond-scale, zero-jitter demands of synchronous AI collectives.
Spectrum-X Ethernet rewrites the networking rulebook. By decoupling and hardware-accelerating the key control loops with adaptive routing within the fabric, targeted congestion control at the transport layer, and PLB at the host edge, Spectrum-X Ethernet delivers the predictable, stable, and ultra-low-latency performance that giga-scale AI demands. Additionally, Spectrum-X Multiplane technology provides a robust, highly resilient, and operationally visible network fabric that simplifies cluster scaling, protects multi-tenant workloads, and minimizes “Time-to-AI”. For any organization building an AI factory, Spectrum-X Ethernet is not just a performance optimization—it is an architectural necessity.
To learn more about Spectrum-X Ethernet and Spectrum-X Multiplane, read the published whitepaper here.
- Khashab, S., et al. (2025). “High-Speed Networking for Giga-Scale AI Factories.” NVIDIA Technical White Paper
- Bai, W., et al. (2023). “Empowering Azure Storage with RDMA.” Proceedings of the USENIX Symposium on Networked Systems Design and Implementation (NSDI)
- Gangidi, A., et al. (2024). “RDMA over Ethernet for Distributed Training at Meta Scale.” Proceedings of the ACM SIGCOMM Conference
- DeepSeek-AI. (2024). “DeepSeek-V3 Technical Report.” arXiv preprint
- Khashab, S., et al. (2025). “NSX: Large-Scale Network Simulation on an AI Server” Proceedings of the ACM Conference on AI Networking
决策记录链 · 只追加
每次领取产生一条记录,重新决策追加一条并以 supersedes 指向被替代的记录(ADR 0014)。
这条决策早于决策账本(2026-10-08 起逐条追加),没有追加记录。