6.5.18 · D4Advanced & Emerging Architectures

Exercises — Co-packaged optics trends

2,429 words11 min readBack to topic

The only formula you truly need is the one from the parent note. Let us re-earn it from zero so nothing is assumed.

Two more tools we will use, defined before we touch them:


Level 1 — Recognition

L1.1

Which of these lives on the same package substrate as the switch ASIC in a CPO design: (a) a QSFP-DD faceplate module, (b) the optical engine, (c) the External Laser Source?

Recall Solution

Answer: (b) the optical engine. By definition, co-packaged optics places the optical engine (modulators + photodetectors + short-reach SerDes/driver) on the same package as the ASIC. A QSFP-DD sits at the faceplate (that is exactly what CPO removes). The External Laser Source (ELS) is deliberately kept outside the hot package so a failed laser can be swapped — so it is not on the package. Only (b) qualifies.

L1.2

Order these by electrical reach, shortest first: Pluggable, On-board optics (OBO), Co-packaged optics.

Recall Solution

Shortest → longest: CPO (1–5 mm) < OBO (5–10 cm) < Pluggable (10–30 cm). The whole point of the integration spectrum is that moving optics closer to the die shrinks the electrical journey. CPO is the shortest of these three (only monolithic optical I/O, at 0, is shorter).

L1.3

Convert into joules per bit. Convert into bits per second.

Recall Solution

(because "pico" = ). (because "tera" = ). These are the two numbers you will drop straight into next level.


Level 2 — Application

L2.1

A 51.2 Tb/s switch uses faceplate SerDes at . Compute the electrical-interface power .

Recall Solution

Multiply the mantissas: . Multiply the powers of ten: . What it means: 256 W just for electrical I/O, on top of the switch core — the "SerDes tax" the parent note warns about.

L2.2

Same switch, but CPO shrinks the reach so . Compute and the fractional saving vs. L2.1.

Recall Solution

Saving . Read carefully: this 80% is only the SerDes-reach portion under this idealized assumption. Whole-link saving is a more honest 30–50% (see L2's trap).

L2.3

Bandwidth doubles to 102.4 Tb/s. At the same CPO , what is ?

Recall Solution

Because is linear in at fixed , doubling bandwidth exactly doubles power ( W). The scary part the parent note flags is that in the real world also rises with line rate, so power grows faster than this clean doubling.

L2.4

A copper trace has loss at the operating frequency. Faceplate reach is ; CPO reach is (3 mm). Compute both dB budgets and the reduction.

Recall Solution

Use (loss is linear in length). Faceplate: . CPO: . The equalizer must recover vs only — a smaller budget. That is why CPO can use a tiny, low-power SerDes: there is almost nothing to equalize.


Level 3 — Analysis

L3.1

Two designs move the same 51.2 Tb/s: (A) faceplate at , (B) LPO that removes the DSP and reaches while keeping the pluggable form factor. Compute B's power, its saving vs A, and argue when you'd pick B over full CPO.

Recall Solution

Saving vs A: . Analysis: LPO captures half the link power (vs CPO's idealized 80% SerDes-slice) but keeps the pluggable form factor — so you retain field serviceability and per-port reach/speed mixing. Pick LPO when serviceability and modularity matter more than the last increment of power; pick CPO when you are power/faceplate-limited and can accept a sealed, non-serviceable switch.

L3.2

The parent note says loss grows like . At low frequency which term dominates, and at very high frequency which? What does that imply as lanes move 112 → 224 Gb/s?

Recall Solution

Compare growth rates. For small , (skin effect) is larger than (dielectric), so the skin-effect term dominates. As grows, the linear term eventually overtakes (a line beats a square-root), so the dielectric term dominates at very high frequency. Implication: doubling the lane rate Gb/s pushes the signal energy up in frequency where the fast-growing dielectric term rules — loss climbs disproportionately. That is precisely "where copper reach really breaks," motivating CPO / short-reach SerDes.

L3.3

A ring-modulator resonance drifts . If co-locating on the hot ASIC raises the optics temperature by , how far does resonance drift, and why is this the central CPO headache?

Recall Solution

Drift . A ring only passes light near its resonant wavelength; a 3 nm shift can move it off the laser's channel entirely, killing the link. Faceplate optics sit in cool, controlled air; CPO glues the optics to a die dumping hundreds of watts. That is why thermal management (and keeping the laser external) is the make-or-break engineering problem — not the pJ/bit math, which is the easy part.


Level 4 — Synthesis

L4.1

Build a total-power model. A 51.2 Tb/s switch has core power . Case A: faceplate I/O at . Case C: CPO I/O at . Compute total power each case and the system-level saving (not just the I/O slice). Then explain why the honest headline is smaller than 80%.

Recall Solution

I/O powers (from L2): , . Totals: System saving . Synthesis point: the same absolute 204.8 W saving is 80% of the I/O slice but only ~37% of the total, because the 300 W core is untouched. This is exactly why the parent note's honest headline is ~30–50% whole-system, not 80%.

L4.2

Sketch (as a Mermaid flow) the decision an architect makes among Pluggable, LPO, and CPO, driven by three factors: power budget, serviceability need, faceplate/density limit.

Recall Solution
flowchart TD
  A["Start: choose optics strategy"] --> B["Is power budget the hard limit"]
  B -->|no| C["Keep Pluggable QSFP-DD or OSFP"]
  B -->|yes| D["Must optics be field serviceable"]
  D -->|yes| E["Use LPO keep pluggable trim DSP"]
  D -->|no| F["Is faceplate density also limiting"]
  F -->|no| E
  F -->|yes| G["Go Co-packaged Optics sealed max density"]

Reading it: power pressure is the gate; if you also refuse to lose serviceability you land on LPO; only when you accept a sealed switch and need faceplate density does full CPO win. This encodes the L3.1 and L3.3 trade-offs into one path.


Level 5 — Mastery

L5.1

Design target: an architect wants total switch I/O power at . What end-to-end (pJ/bit) must the optical I/O hit? Is that within the parent note's stated CPO targets? Defend the answer.

Recall Solution

Invert the engine: . Defence: the parent note's CPO target is < 5 pJ/bit end-to-end, aiming toward ~1 pJ/bit optical I/O. Requiring is below even the ~1 pJ/bit aspiration — so this budget is more aggressive than current CPO goals. It's physically the right direction (short reach + silicon photonics) but demands better-than-state-of-the-art efficiency; the architect should either relax the budget toward ~100 W (giving ~1 pJ/bit) or wait for monolithic optical I/O.

L5.2

Mastery synthesis: at , compare (i) faceplate 5 pJ/bit, (ii) LPO 2.5 pJ/bit, (iii) CPO 1 pJ/bit. Give each I/O power and each saving vs faceplate. Then state, in one sentence each, the non-power cost you accept moving down the list.

Recall Solution

Using :

  • (i) Faceplate: — baseline.
  • (ii) LPO: → saving .
  • (iii) CPO: → saving .

Non-power costs accepted going down:

  • Faceplate → LPO: you lose the safety of on-module DSP; the link now depends on the host SerDes equalizing a longer channel (a link-budget risk), but keep the pluggable body.
  • LPO → CPO: you lose field serviceability and modularity — the optics are sealed onto the package substrate, and a dead engine can mean scrapping the switch, while the hot ASIC now threatens optical thermal stability. Verdict: power savings and integration risk rise together; there is no free lunch, only a chosen point on the curve.

Recall One-line self-check

Why is the CPO whole-switch saving (~37% in L4.1) so much less than the I/O-slice saving (80%)? ::: Because the untouched switch core power sits in the denominator of the whole-switch percentage but not in the I/O-slice percentage — same joules saved, bigger base.

See also: Switch ASIC Bandwidth Scaling · Data Center Network Topologies · Co-packaged optics trends