clm_36db5244b4b242ffa441616bb53cc373_r1

NIEK2-0190

① SA Source

• Source: 開啟完整 SA 文章
• Section: Nvidia’s CPO Roadmap
• Line hint: 213

Context Before

Source: SemiAnalysis AI Networking Model ↗, Nvidia

Evidence

CPO scale-up will be used to build the larger world size, connecting between the racks in a two-tier all to all network, though scale-up inside the racks will remain copper-based

Context After

When we reach the Feynman Generation, CPO usage will expand via another large world size rack, the NVL1152 which is formed by combining 8 Kyber racks. While the Nvidia Technical Blog ↗ that outlines the rack configuration roadmap states that “NVIDIA Kyber will scale up into a massive all-to-all NVL1152 supercomputer using similar direct optical interconnects for rack-to-rack scale-up”, Jensen Huang in a Financial Analyst Q+A session did say that NVL1152 in Feynman would be “all CPO”. There is some disagreement on whether copper will still be used for scale-up within the rack or whether CPO will replace copper.

Nvidia’s approach has been to use copper where they can, and optics where they must. The architecture of NVL1152 in the Feynman generation will follow the same principle. It is clear that the NVL1152 will adopt CPO to connect between racks, but from GPUs to NVLink Switches is currently copper POR. Nvidia is unable to achieve another doubling of electrical lane speed from 224Gbit/s bi-di to 448Gbit/s uni-di means bandwidth isn’t that amazing.

② Atomic Claim

較大的 world-size 會以 CPO scale-up 建構，機櫃之間採兩層 all-to-all network，但機櫃內 scale-up 仍維持 copper。

• Epistemic Mode: ASSERTED
• Mapping Status: PARTIAL

③ Semantic Frame

{
  "comparison_expression": "較大的 world-size 會以 CPO scale-up 建構，機櫃之間採兩層 all-to-all network，但機櫃內 scale-up 仍維持 copper。",
  "entities": [
    {
      "id": "04_knowledge_base/CPO",
      "label": "CPO"
    },
    {
      "id": "04_knowledge_base/Copper",
      "label": "copper"
    }
  ],
  "frame_type": "COMPARISON",
  "metric": "UNSPECIFIED_METRIC",
  "operator": "UNSPECIFIED_COMPARISON",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
comparison_entity_0	CPO	CPO
comparison_entity_1	copper	Copper

⑤ Human Review

請在 Properties 逐項確認：

• 原文 → Atomic Claim 是否忠實
• Atomic Claim → Semantic Frame 是否忠實
• Canonical Entity mapping 是否正確
• Epistemic mode 是否保留原文語氣
• 最後選擇 review_action

Review state

Markdown 內文不是正式 approval。只有 Apply bridge 寫入的 Decision Ledger event 才是正式決策。