Broadcom의 Tomahawk 6는 대역폭을 두 배로 늘리지만, AI 네트워크는 여전히 확장성 압박에 직면해 있다.

Broadcom Tomahawk 6 doubled single-chip Ethernet switching capacity to 102.4 terabits per second, yet that advance does not automatically double an AI cluster's useful capacity. Faster connections can consume the extra bandwidth before operators connect more accelerators. The resulting pressure reaches beyond switches into building layouts, software, and deployment schedules.

An October 30 opinion piece in *Data Center Dynamics* brought that tension back into focus. Its author, Eridu co-founder Omar Hassen, argues that networking must shape AI facilities from the beginning. His warning deserves attention, alongside scrutiny of the timeline and assumptions behind it.

Broadcom and Nvidia are already responding with faster switching and optical integration. Meta's engineering work adds another consideration: installed bandwidth and usable bandwidth are different things. The central conflict is between growing communication requirements and the network's ability to deliver predictable application performance.

**Broadcom Tomahawk 6 Changes the Numbers, Not the Entire Equation**

The latest bandwidth increase is real, but it does not establish that the network constraint has disappeared.

Broadcom announced that it was shipping Tomahawk 6 on June 3, 2025. Its stated capacity was 102.4 terabits per second, a measure of aggregate data movement through the switch chip. The company also described routing and connectivity features intended for AI infrastructure.

That announcement matters when assessing the recent "network wall" argument. Hassen presents insufficient switch bandwidth and connectivity as constraints on productive AI infrastructure. He advocates higher connectivity and flatter networks, meaning designs with fewer switching layers.

The article is a vendor executive's analysis rather than an independent measurement of the entire market. That distinction does not invalidate its thesis. It does mean readers should separate the architectural argument from claims about industry progress.

The timing needs particular care. Broadcom's Tomahawk 5 launch dates to August 16, 2022, when the company announced 51.2-terabit switching capacity. The next announcement followed in June 2025, less than three years later.

Those dates do not support treating the chip announcement interval as almost four years. They also cannot establish when complete systems became broadly available or entered production. Silicon shipment, equipment qualification, and operational deployment represent different milestones.

This distinction changes the question buyers should ask. The issue is not simply whether switch manufacturers are doubling capacity. It is whether deployable systems provide enough useful connectivity at the speeds required by the intended workload.

A faster chip creates design options. Operators can allocate its capacity toward faster connections, more connections, or a combination of both. Packaging, equipment design, and supported configurations determine which options become practical products.

Consequently, a bandwidth milestone should begin an architectural assessment rather than end one. Buyers need to connect the chip specification to the equipment they can procure, then connect that equipment to application behavior.

The same caution applies to claims that networking has fallen irreversibly behind computing. There is no universal ratio that describes every model, cluster, or deployment. Some applications exchange data frequently; others keep more work local.

The defensible conclusion is narrower and more useful. Switching capacity has advanced, but capacity alone remains an incomplete description of AI infrastructure. The pressure emerges where workload communication requirements exceed the network's practical ability to serve them.

**Faster Ports Can Absorb the Entire Bandwidth Gain**

A switch can become faster without connecting more accelerators at the required speed.

The crucial distinction is between total bandwidth and radix, the number of independent connections a switch supports at a specified speed. Neither number makes sense without the other. A high connection count at a lower speed does not describe the same capability as that count at a higher speed.

The arithmetic explains why switch bandwidth scaling can disappoint infrastructure planners. If aggregate capacity doubles while the required bandwidth per connection also doubles, the theoretical connection count stays unchanged. This is a conditional relationship, not a measured claim about every shipping switch.

That relationship matters because AI facilities must accommodate both communication speed and cluster size. Meeting one requirement can consume the resources intended for the other. Operators cannot assume a new switch generation expands both dimensions equally.

A physical connector adds another complication. It does not always correspond to one independent accelerator connection. Equipment can combine channels into faster links or divide supported connections through breakout arrangements.

Buyers therefore need the supported configuration rather than a headline connector count. They also need to know how many connections serve accelerators and how many connect switches. Capacity allocated between switching layers cannot simultaneously serve an endpoint.

Broadcom's Tomahawk 6 specifications illustrate why configuration details matter. The company describes a two-tier network supporting more than 100,000 accelerators at 200 gigabits per second per link. That is a vendor design claim tied to a stated connection speed, not a universal cluster guarantee.

The speed qualification belongs beside the scale figure. Removing it makes comparisons misleading. A design supporting a large endpoint population at one speed cannot automatically support the same population at a higher speed.

The same discipline applies to switch layers. Adding another layer can extend a network, but it also introduces more equipment and connections. Whether that trade is acceptable depends on the traffic crossing it.

A larger network is not necessarily slower in every useful sense. Additional paths can provide capacity and resilience when the design and software use them effectively. Equally, fewer layers do not guarantee better application performance.

The practical constraint is the communication pattern the network must sustain. A design might handle localized traffic well while struggling when applications communicate across distant groups. Aggregate bandwidth can obscure that difference.

This is why comparing switch generations requires more than checking whether the capacity doubled. The meaningful comparison holds endpoint speed, workload, resilience requirements, and topology constant. Topology means the arrangement of devices and links.

Without those conditions, switch bandwidth scaling can look impressive while leaving the operational problem largely unchanged. With them, buyers can identify which part of the design actually benefits.

**The Pressure Falls on Cluster Owners Before Application Users**

Network limitations become an operating problem when paid-for computing capacity waits for communication.

Consider a distributed training job, where multiple accelerators cooperate to update one model. Each accelerator performs part of the computation. At designated points, participants exchange information before continuing.

A collective operation coordinates that exchange across a group of processors. All-reduce, for example, combines contributions and distributes the combined result. Its completion depends on the communication required by the group.

The important consequence is coordination. An accelerator that finishes its local work cannot always advance independently. Delayed communication can extend the time before useful computation resumes.

This does not mean networking explains every idle accelerator. Data preparation, software behavior, memory limits, and scheduling can also restrict performance. Assigning all underutilization to the network would obscure the actual diagnosis.

For a cluster owner, the relevant question is which constraint controls job completion. Faster switches have limited value when another resource determines the pace. Conversely, faster processors offer less benefit when communication remains on the critical path.

That creates pressure on infrastructure planning. Procurement teams can purchase accelerators and networking through separate processes, but the application experiences them together. A mismatch becomes visible during workload execution, after equipment decisions have already constrained the available remedies.

The same relationship appears in inference, the process of running a trained model to generate an output. When a model spans accelerators, communication becomes part of serving the request. Its importance depends on how the application divides the work.

Mixture-of-experts models select specialized model componen

[Source text ends mid-sentence.]