Zach Busch

Ultra-High-Speed Optical Fiber Communication for Massively Parallel AI Processing

Zach Busch, Nicholas Gazzara, Jonas Craig

ENGR 113 First-Year Engineering Design, Drexel University, Spring 2026

Instructor: Dr. Afshin S. Daryoush

Placed 2nd of 10 teams

Abstract

This first-year engineering design project developed an ultra-high-speed optical fiber communication system for massively parallel AI processing. Data centers must scale in bandwidth, efficiency and cost, which drives the need for better communication architectures. The project aimed to maximize optical link performance while remaining cost-effective. Key challenges included defining the system architecture, selecting photonic and computer hardware, and creating a clear, readable block diagram. Although NVIDIA hardware was initially considered for the whole system, Infinera (now Nokia) optical solutions were ultimately chosen for their scalability. The final design links 4,608 GPUs (64 NVL72 racks), each with an 800 Gb/s optical link. Technical work included calculating signal-to-noise ratio (SNR), bit error rate (BER), bandwidth and latency, along with environmental and cost analysis.

1Problem overview

In the last few years, large language models have grown rapidly in popularity, creating a large demand for high-performance computing among consumers and industry alike. As AI models have become significantly more advanced, they have also become increasingly complex. Today, AI training workloads can require thousands of flagship, high-power GPUs. These GPUs are configured in servers to maximize bandwidth and create fast connections from GPU to GPU, so they can constantly exchange model parameters, gradients and training data. Because of this data transfer requirement, the system connecting the GPUs has become nearly as important as the GPUs themselves.

This GPU-to-GPU communication has become much more complicated in recent years. Today, communication occurs across multiple “layers” within an AI computing architecture, from communication within a rack to rack-to-rack, pod-to-pod and finally building-to-building. Technologies such as NVLink Gen 5 have heavily optimized communication within servers and racks; NVIDIA describes one NVL72 rack as “essentially one giant GPU.”1 Communication between pods and buildings, however, still has significant room for improvement. It is commonly handled with Ethernet or InfiniBand, in large deployments built on fat-tree and Clos network architectures. These provide high performance, but often at the cost of increased complexity and reduced scalability as systems continue to grow.

As AI systems grow, more data must be moved from rack to rack, pod to pod and building to building. As physical link lengths increase, latency, BER and power consumption can increase significantly, and each additional network layer built on Ethernet or InfiniBand adds complexity while reducing overall scalability. Consequently, many companies are searching for faster, more efficient and more scalable methods of data communication.

2Why optical fiber

One of the most promising solutions is optical fiber communication. Optical fiber can provide significantly higher bandwidth than traditional copper connections while maintaining very low attenuation over long distances. A technology known as wavelength-division multiplexing (WDM) allows multiple independent data channels to operate simultaneously on a single fiber, which improves scalability while helping reduce overall power consumption.

Because future AI systems will require scalable, high-bandwidth communication between racks, pods and buildings, optical networking architectures have emerged as a promising way past the limits of traditional electrical interconnects.

Key terms

Single-mode fiber
Fiber that carries a single light path. It loses about 0.2 dB per kilometer near 1550 nm, while passive copper reaches only a few meters at 100+ Gb/s per lane.
Dense WDM (DWDM)
WDM with channels spaced 100 GHz (about 0.8 nm) or 50 GHz apart in the C-band (1530-1565 nm), giving 40 to 80 or more channels on one fiber.
PAM4
A signal with four levels, carrying 2 bits per symbol, so 53 GBd gives about 106 Gb/s per lane. Each eye opening is a third as tall as in two-level signaling, a penalty of about 9.5 dB in SNR,14 which is why these links use forward error correction.
Coherent optics
Transmission that encodes data in the amplitude, phase and polarization of light, with a DSP chip correcting fiber distortion. It carries 800 Gb/s to 1.2 Tb/s per wavelength.5
Optical circuit switching (OCS)
A switch that steers light from any input fiber to any output fiber without converting it to electrical (O-E-O). Reconfiguring takes milliseconds, which suits long-lived traffic such as AI training. Google has used OCS in production since TPU v4.8

3Existing solutions

Many companies have invested significant time and resources into researching AI communication architectures. NVIDIA has developed systems using NVLink and NVSwitch for high-bandwidth communication within servers and racks, and commonly uses InfiniBand in large deployments built around fat-tree (Clos) architectures. Google has approached the challenge through TPU pods, which use torus-based interconnects designed to support distributed AI training. Microsoft has addressed similar challenges with Ethernet leaf-spine architectures. Each of these approaches supports modern AI workloads; however, as AI systems continue to grow in size and complexity, these solutions become increasingly expensive and difficult to scale (Table 1).

Table 1.Existing approaches to GPU networking at scale.

CompanyApproachStrengthWhere it strains at scale
NVIDIANVLink + NVSwitch inside the rack; InfiniBand in fat-tree (Clos) networks between racksVery high bandwidth; mature ecosystemEvery switch tier adds switches, transceivers and O-E-O conversions, so cost and power grow with each layer
GoogleTPU pods on a torus interconnect, reconfigured by in-house optical circuit switches (TPU v4: 4,096 chips per pod7)OCS and optics under 5% of system cost and power8Custom, in-house hardware
MicrosoftEthernet leaf-spine networksStandard, multi-vendorSame multi-tier switching overhead as systems grow

Optical networking technologies are already widely used throughout telecommunications and internet backbone infrastructure, and technologies such as WDM, coherent optics and photonic integrated circuits are being actively researched for future AI networking. These trends point to a growing demand for scalable optical communication systems that can support next-generation AI workloads, which motivated the architecture in this project. Recent industry developments:

  • 2023. Google publishes TPU v4, the first production supercomputer with reconfigurable optical circuit switching.7
  • Feb 2025. Nokia completes its acquisition of Infinera, the maker of this project’s Layer 4 transport hardware.15
  • Mar 2025. NVIDIA announces Spectrum-X and Quantum-X Photonics switches, with the optics co-packaged inside the switch package, claiming 3.5× better power efficiency.9
  • 2025. HUBER+SUHNER opens a new POLATIS optical-circuit-switch factory for AI data centers and plans at least 5× more capacity.16

4The architecture

Our objective was to develop a scalable communication architecture for large AI computing systems. The design combines pre-existing commercial products and established networking concepts into one unified, scalable model with four layers (Figs. 1 and 2). Layer 1 uses NVIDIA’s GB300 compute trays as the primary compute layer, and Layer 2 uses NVIDIA’s NVL72 rack architecture for high-bandwidth copper connections between those trays. Both are preconfigured and deeply optimized by NVIDIA already. Layers 3 and 4 are where our research was primarily focused: a HUBER+SUHNER POLATIS Series 7000 optical circuit switch connects racks and pods inside the building, and the Nokia (formerly Infinera) 1830 GX G42 with FlexILS DWDM transport carries data between buildings.

To evaluate the design, we considered bandwidth, latency, SNR and BER, along with cost, reliability, scalability and implementation complexity.

LevelHoldsUnitGPUs in one
L1Compute tray4GPUs per tray4 GPUs
L2NVL72 rack×18trays per rack72 GPUs
L3Pod×8racks per pod576 GPUs
L4Building×8pods per building4,608 GPUs

4 × 18 × 8 × 8 = 4,608 GPUs in a building: 64 racks and 1,152 compute trays.

Figure 1.Units at each level and the number of GPUs in one.

Table 2.Hardware and estimates for each layer.

LayerHardwareEstimate
L1 ComputeNVIDIA GB300 compute tray112 Gb/s per electrical lane; ~20 ns per hop
L2 RackNVIDIA GB300 NVL72800 Gb/s per link (8 lanes × 53 GBd PAM4); ~6 dB loss budget; SNR ~34 dB per lane; ~0.5 µs per fabric hop
L3 Pod optical fabricHUBER+SUHNER POLATIS Series 7000 OCSFiber runs ≤1 km; ~4 dB loss budget; SNR ≈ L2 (~34 dB)
L4 Optical transportNokia (formerly Infinera) 1830 GX G42 + ICE-X + FlexILS~10 km link; ~10 dB loss budget; SNR ~25-30 dB; ~80 µs building-to-building

5Following the data

L1 Compute. Data starts processing at Layer 1, the GB300 compute tray. Each tray has 4 B300 Blackwell GPUs wired to 2 Arm-based Grace CPUs, which communicate over NVIDIA’s NVLink-C2C, an ultra-high-bandwidth, low-latency chip-to-chip connection. These trays are vital to the entire architecture: the rest of it is designed to connect them to each other on a massive scale. Because of that scale, the bottlenecks sit in Layers 2 to 4, which are designed to reduce them as much as possible.

L2 Rack. At Layer 2, each compute tray connects to the NVL72 rack spine. The spine uses NVIDIA’s NVLink Gen 5 to likewise maximize bandwidth and minimize latency, clustering 18 trays (72 GPUs) into one rack. This layer is already designed and optimized by NVIDIA. Data leaves the NVL72 rack as 800 Gb/s PAM4 over single-mode fiber at 1310 nm.

L3 Pod optical fabric. At Layer 3, we selected the POLATIS Series 7000 optical circuit switch, specifically to maximize bandwidth. It receives all the aggregated traffic from the NVL72 racks, connecting racks within a pod and pods within the building. Because the switch is entirely optical, the signal is never converted to electrical, which keeps signal quality high. The switch is also non-blocking, allowing multiple optical paths to exist at once without creating network congestion. This capability is primarily why we chose this model. Layer 3 outputs the same single-fiber PAM4 signal at 1310 nm that came in, adding about 25 ns.4

L4 Optical transport. Finally, at Layer 4 the objective switches from low-latency switching to long-distance data transmission. The PAM4 data goes into the Nokia 1830 GX G42 transport platform, where ICE-X coherent optics convert it into DWDM channels for transmission to a remote building about 10 km away, and FlexILS combines those channels onto one fiber. This is the only optical-electrical-optical conversion in the design, and it applies only to traffic leaving the building.

Light travels through glass at about 2×10⁸ m/s (5 ns per meter), so over building-scale distances, propagation is the largest part of the latency.

6Engineering analysis

Jonas Craig led the engineering calculations. Each layer was analyzed with first-order hand calculations of bandwidth, SNR, BER, optical loss and latency, using standard textbook models, to check that the design is feasible.

Bandwidth came out to 112 Gb/s per lane for Layer 1 and 800 Gb/s for Layers 2 and 3. These are per-link (per-GPU) figures.

Table 3.Per-layer estimates.

LayerLinkBandwidthSNR (est.)BER (est.)Loss budgetLatency
L1 Compute trayElectrical, ~0.5 m112 Gb/s per lane~62 dB10⁻¹⁵-10⁻¹⁸ (assumed)n/a (electrical)~20 ns / hop
L2 Rack egress1310 nm PAM4, SMF, ~50 m800 Gb/s~34 dB per lane~10⁻¹² (target, after FEC)~6 dB~0.5 µs / hop
L3 POLATIS OCS1310 nm PAM4, SMF, ≤1 km~800 Gb/s≈ L2≈ L2~4 dB~0.5-5.5 µs (≤1 km of fiber + ~25 ns switch)
L4 Nokia GX DWDMCoherent DWDM, ~10 km~800 Gb/s per channel~25-30 dB≈ L2~10 dB~80 µs building-to-building

Figure 3.Optical loss budget by layer

L2Rack egress

≈6 dB7 dB
  • Fiber ≈0
  • Connectors and patch panels 5.5
  • Available budget: 0 dBm Tx − (−7 dBm) Rx sensitivity

L3POLATIS OCS

≈4 dB
  • Fiber 0.2
  • Connectors and splices 2.5
  • OCS insertion 1

L4Nokia GX DWDM

≈10 dB
  • Fiber 2
  • Connectors, splices and patches 3.5
  • ROADMs 4
Most of the loss comes from connectors and patch panels. The fiber itself adds little, and the rack-egress link has about 1 dB of margin.

Figure 4.Latency by layer (log scale)

L1Compute tray, per hop

20 ns

L2Rack egress, per hop

0.5 µs

L3POLATIS OCS

0.5-5.5 µs

L4Building to building

~80 µs
Building-to-building latency is about 4,000 times a single in-tray hop; 50 µs of the roughly 80 µs is propagation through 10 km of fiber. The lighter part of the Layer 3 bar shows the range from a short link inside a pod (about 0.5 µs) to a 1 km link (about 5.5 µs).

Box 1.Example: Layer 1 signal-to-noise ratio

Signal: 0.4 V single-ended swing into 50 Ω

Vrms = 0.4 / (2√2) ≈ 0.14 V

Psignal = Vrms2 / R = 0.142 / 50 ≈ 4.0 × 10−4 W (≈ −4 dBm)

Noise: thermal (kTB), T = 300 K, B = 56 GHz (half the 112 Gb/s lane rate)

Pnoise = 1.38×10−23 · 300 · 56×109 ≈ 2.3 × 10−10 W

SNR = 4.0×10−4 / 2.3×10−10 ≈ 1.7 × 106 → ≈ 62 dB

Latency: tser = 256 bits / 112 Gb/s ≈ 2.3 ns ; tprop = 0.5 m / 2×108 m/s = 2.5 ns

Box 2.Example: Layer 2 signal-to-noise ratio

Received power per lane: 0 dBm launch − 6 dB link loss = −6 dBm ≈ 2.5 × 10−4 W

Photocurrent, with a 0.8 A/W photodiode: I = R·P ≈ 2.0 × 10−4 A

Thermal noise current in 50 Ω, B = 50 GHz:

σ2 = 4kTB / R = 4 · 1.38×10−23 · 300 · 50×109 / 50 ≈ 1.66 × 10−11 A2

SNR = I2 / σ2 = (2.0×10−4)2 / 1.66×10−11 ≈ 2.4 × 103 → ≈ 34 dB

Shot noise (2qIB ≈ 3.2 × 10−12 A2) lowers this to about 33 dB.

Limitations

  • Noise is modeled as thermal (plus shot noise at Layer 2). Real optical links are also limited by laser intensity noise, receiver amplifier noise and, over distance, optical amplifier noise, all of which lower SNR further.
  • Real 800G links run at a raw (pre-error-correction) BER far above 10⁻¹² and rely on forward error correction (FEC) to reach the ~10⁻¹² target.
  • The OCS loss uses 1 dB; the POLATIS datasheet lists 1.5 dB typical and 2.7 dB maximum.4 Fiber loss at 1310 nm is closer to 0.35 dB/km than 0.2. Over ≤1 km, both change the Layer 3 budget by less than 2 dB.

7Scale and cost

18 trays per rack, 8 racks per pod and 8 pods per building: 64 racks, 1,152 compute trays and 4,608 GPUs.

Table 4.Estimated hardware cost.

LevelWhat’s includedEstimated cost
One NVL72 rack18 GB300 trays + NVLink fabric~$2.7M - $3.6M
One pod8 racks + pod networking~$22M - $30M
Full system64 racks (1,152 trays) + optical fabric (OCS) + InfiniBand cluster networking~$180M - $250M

At roughly $180-250 million, a system at this scale is marketable only to very large organizations, such as hyperscale cloud providers and national laboratories, rather than the average data center company. It could be scaled down by condensing the layers and using less hardware, but with a significant loss in performance for the end user.

8Energy and impact

Nicholas Gazzara led the environmental impact and infrastructure analysis. The architecture has both sustainability benefits and broader societal impacts. By using optical networking technologies like optical circuit switching (OCS) and dense wavelength-division multiplexing (DWDM), the system can transmit large amounts of data more efficiently, reducing the need for additional physical infrastructure and lowering network power consumption. However, the system still operates at a very large scale. Each NVL72 rack draws roughly 120 kW,17 so 64 racks and 1,152 compute trays come to about 8 MW of continuous computing load and significant heat. That requires advanced cooling and increases both energy and water use, making efficiency a critical factor in the design.

As data centers continue to expand to support AI workloads, their impact on electricity use and carbon emissions grows. U.S. data centers used 58 TWh in 2014 and 176 TWh in 2023, about 4.4% of the national total.10 Federal projections put national data center use at 325-580 TWh by 2028, between 6.7% and 12% of U.S. electricity (Fig. 5).11 While systems like this enable major advances in research, healthcare and automation, they also show the importance of balancing high-performance computing with responsible energy use and long-term sustainability.

Figure 5.U.S. data center electricity use, 2014-2028

U.S. data center electricity use, 2014-2028, in TWh and share of U.S. electricity
YearTWhShare
201458-
2018761.9%
20231764.4%
2028 (projected)325-5806.7%-12%
Data: Lawrence Berkeley National Laboratory, 2024 United States Data Center Energy Usage Report (Dec 2024).10

9Design decisions and next steps

  1. Build on NVIDIA’s rack. Layers 1 and 2 are preconfigured and deeply optimized by NVIDIA already, so our research focused on Layers 3 and 4, where communication between pods and buildings still has room for improvement.
  2. Optical circuit switching at Layer 3. We chose the POLATIS switch specifically to maximize bandwidth. It is entirely optical, so signal quality is preserved, and it is non-blocking, so many paths can be open at once. Reconfiguring takes about 50 ms,4 so the switch suits long-lived flows; the full system keeps an InfiniBand cluster network for traffic that needs per-packet switching.
  3. Coherent DWDM at Layer 4. Although NVIDIA hardware was initially considered, we chose Infinera (now Nokia) optical transport for its scalability. At building scale, the objective switches from low-latency switching to long-distance transmission, and DWDM puts many 800 Gb/s channels on a single fiber.
  4. Commercial parts only. The design combines pre-existing commercial products and established networking concepts into one unified, scalable model that can be built with hardware available today.
  5. Next steps. A full-size version needs to be tested with all the servers in place, to measure how much electricity the system draws while running AI workloads and how much heat it adds. The analysis should also be extended to a full link budget that includes all major noise sources and forward error correction, along with a power model for each layer.

10Contributions

Zach Busch led the system design, defined the four-layer hierarchy, selected the hardware for each layer, worked out how data moves between the layers, and built the architecture diagram.

Jonas Craig led the engineering calculations of bandwidth, SNR, BER, optical loss and latency for each layer.

Nicholas Gazzara led the environmental impact and infrastructure analysis, covering cost, power, cooling and energy use.

Course. ENGR 113 First-Year Engineering Design, Drexel University

Instructor. Dr. Afshin S. Daryoush

Result. Placed 2nd of 10 teams, ranked by the instructor.

References

  1. NVIDIA, “GB300 NVL72.” nvidia.com (opens in a new tab)
  2. NVIDIA, “NVL72 AI Factory reference architecture: system hardware and components.” docs.nvidia.com (opens in a new tab)
  3. HUBER+SUHNER, “POLATIS 7000 Optical Circuit Switch.” hubersuhner.com (opens in a new tab)
  4. HUBER+SUHNER, “POLATIS Series 7000n datasheet.” lasercomponents.com (opens in a new tab)
  5. Nokia, “1830 Global Express (GX).” nokia.com (opens in a new tab)
  6. Nokia, “1830 Flexible Intelligent Line System (FlexILS).” nokia.com (opens in a new tab)
  7. N. P. Jouppi et al., “TPU v4: An Optically Reconfigurable Supercomputer for Machine Learning with Hardware Support for Embeddings,” ISCA 2023. arxiv.org (opens in a new tab)
  8. Google Cloud, “TPU v4 enables performance, energy and CO2e efficiency gains.” cloud.google.com (opens in a new tab)
  9. NVIDIA, “NVIDIA Announces Spectrum-X Photonics, Co-Packaged Optics Networking Switches…,” Mar. 18, 2025. investor.nvidia.com (opens in a new tab)
  10. A. Shehabi et al., “2024 United States Data Center Energy Usage Report,” LBNL, Dec. 2024. eta-publications.lbl.gov (opens in a new tab)
  11. U.S. DOE, “DOE Releases New Report Evaluating Increase in Electricity Demand from Data Centers.” energy.gov (opens in a new tab)
  12. D. Foley and J. Danskin, “Ultra-Performance Pascal GPU and NVLink Interconnect,” IEEE Micro, 2017. doi.org (opens in a new tab)
  13. C. Gómez et al., “Beyond Fat-tree: Unidirectional Load-Balanced Multistage Interconnection Network,” IEEE CAL, 2008. doi.org (opens in a new tab)
  14. Keysight, “PAM4 Design Challenges and the Implications on Test.” keysight.com (opens in a new tab)
  15. Converge Digest, “Nokia completes Infinera acquisition,” Mar. 2025. convergedigest.com (opens in a new tab)
  16. Signal Integrity Journal, “HUBER+SUHNER opens new POLATIS optical circuit switch production site to support AI data centers,” 2025. signalintegrityjournal.com (opens in a new tab)
  17. Introl, “Why the NVIDIA GB300 NVL72 (Blackwell Ultra) Matters.” introl.com (opens in a new tab)