← research bank

Optical attach is set by topology, not by shipments — linear optical TAM models are mis-specified

optical-attach-is-topological · conviction medium · status open · horizon 2026-2028 · as of 2026-08-03

Sell-side optical TAM scales optical content with accelerator and rack shipments. The published traffic decomposition says otherwise: ~97% of LLM training traffic is tensor- and sequence-parallel and therefore LOCAL, so a mesh topology reserves optics for pod-to-pod and costs under a third of flat/Clos for the same silicon. Optical content per unit of compute is a function of the topology an operator picks and the training/inference mix it runs — not of how many chips ship.
Robust to undisclosed shares. 1 derived input under this thesis; redrawing every supply weight the industry does not publish moves none of them by more than 25%. Computed from evidence at most 17 days old (oldest input: broadcom).

Exhibits

Exhibit 1Relative performance, indexed to 100How the names in this thesis have traded against SOXX.
-12481974LITE 766COHR 328SOXX 225CRDO 208ALAB 18612mo, indexed to 100 at start · dashed = SOXX benchmark

Series available as data/optical-attach-is-topological.csv

Exhibit 2What the conviction is actually made ofEach premise and the number it composes to. A conjunction of plausible premises is far weaker than any of them.
Optical content is mechanically downstream of topology, and the desk holds both pathsOptical Transceivers (800G/1.6T pluggables)95.0%Optical Transceivers (800G/1.6T pluggables)…100.0%Nvlink95.0%COMPOSED (and)90.2%

90% if the 3 gates are independent, 95% if they move together. They are claims about one industry, so the truth is between and nobody can say where. Treat this as an ordering device rather than a calibrated probability — the ranking of premises is the information, not the level.

Weakest link: Optical Transceivers (800G/1.6T pluggables) at 0.95 — Pluggable optics; the scale-out path.

The traffic structure supports mesh for training, which is the low-optics caseScale-up fabric (within the node / rack)90.0%Scale-out network (between nodes)90.0%Interconnect bandwidth (scale-up and scale-…85.0%COMPOSED (and)68.8%

69% if the 3 gates are independent, 85% if they move together. They are claims about one industry, so the truth is between and nobody can say where. Treat this as an ordering device rather than a calibrated probability — the ranking of premises is the information, not the level.

Weakest link: Interconnect bandwidth (scale-up and scale-out) at 0.85 — The resource both paths deliver, and the node the workload layer consumes.

Therefore linear optical TAM models are mis-specified in BOTH directions, and the tradable question is mixCo-packaged optics75.0%Linear-drive optics (LPO / LRO)60.0%Credo Technology85.0%COMPOSED (and)38.2%

38% if the 3 gates are independent, 60% if they move together. They are claims about one industry, so the truth is between and nobody can say where. Treat this as an ordering device rather than a calibrated probability — the ranking of premises is the information, not the level.

Weakest link: Linear-drive optics (LPO / LRO) at 0.60 — Contested architecture that changes content per port without changing port count. Not settled in the merchant market.

The variant

Consensus

AI optical demand is a monotonic mega-trend. Bandwidth per rack rises 16-45x across the roadmap, copper hits a reach ceiling, pluggables give way to co-packaged optics, and a ~$154bn rack-level optical TAM follows from multiplying content per rack by rack shipments. Optical attach per accelerator is treated as a roadmap constant.

Variant

Attach rate is a DESIGN CHOICE, and the same sell-side data shows it spanning 6-9x. Huawei's CloudMatrix 384 runs 1:18 optical modules per chip because it connects everything optically; NVIDIA's GB300 runs 1:2-3 because NVLink scale-up rides a copper backplane and optics only serve scale-out. The UB-Mesh traffic decomposition explains why the spread exists: tensor-parallel AllReduce ~52.9% and sequence-parallel AllGather ~44.1% of training traffic are highly local, so a mesh can serve them on direct-attach copper and reserve optics for the pod boundary — stated at under one third of flat/Clos networking cost. A training-heavy mesh buildout and an inference-heavy Clos buildout consume very different optical content at identical silicon volume.

Differentiator

Both sides of this argument use the same numbers and neither tracks the variable that reconciles them. The sell-side TAM already ENCODES topology dependence in its own attach table (1:18 vs 1:2-3) and then models the aggregate as if attach were fixed. The desk's edge is holding the reconciliation variable explicitly — training/inference mix and disclosed topology per platform — as the leading indicator for optical attach, and refusing to scale optical demand linearly with accelerator units in either direction.

Falsifiers

Open questions

Reasoning chain

Optical content is mechanically downstream of topology, and the desk holds both paths VALID
premises

Bandwidth can be delivered over copper inside a domain or over fibre between them. Which one carries a given link is a topology decision, so optical content per accelerator is determined at design time, not by unit volume.

The traffic structure supports mesh for training, which is the low-optics case VALID
premises

If ~97% of training traffic is tensor- and sequence-parallel and local, most links never need to leave the copper domain. Optics attach at the boundary, and the boundary's position is set by the topology.

Therefore linear optical TAM models are mis-specified in BOTH directions, and the tradable question is mix VALID
premises

A forecast that scales optics with shipments is right only if mix is constant. It is not: CPO penetration is assumed, LPO is contested, and active copper extends the copper domain. The desk therefore holds attach as a dependent variable and tracks mix, rather than taking a direction on optical volume.

Sources

Write-up

Pre-filled skeleton: optical-attach-is-topological.md