VR2R-0591

回到這篇 SA Coverage

① SA Source

Context Before

image

Source: SemiAnalysis AI Networking Model ↗

Evidence

For the Vera Rubin NVL72 deployment however, there are two 800G OSFP cages per GPU for a total of 1.6T per GPU bandwidth. Having two 800G logical ports per GPU is advantageous because it allows multi-plane network deployments without complex fiber management – by splitting one logical GPU two ways to two different leaf switches. As such, larger network clusters can be built with two 800G logical ports than if only one 1.6T logical port were used. In fact, as we have explained in multiple prior articles such as the networking sections of NVIDIA’s Optical Boogeyman ↗ and Microsoft’s AI Strategy Deconstructed ↗, this relationship is dictated by a simple formula for the maximum number of hosts that can be supported using a switch of k ports on an L-layer:

Context After

2(k2)L

Illustratively, consider two hypothetical VR NVL deployments with 1.6T and 800G logical ports respectively. A 1-plane, 3-layer network with one 1.6T logical ports achieves only a maximum cluster size of 93,312 GPUs, or:

② Atomic Claim

但在 Vera Rubin NVL72 deployment 中,每顆 GPU 有 2 個 800G OSFP cages,因此每顆 GPU 合計 bandwidth 為 1.6T。

  • Epistemic Mode: ASSERTED
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/Vera Rubin",
        "label": "Vera Rubin"
      },
      "role": "platform"
    },
    {
      "node": {
        "id": "04_knowledge_base/GPU",
        "label": "GPU"
      },
      "role": "processor"
    }
  ],
  "qualifiers": {
    "condition_text": "OSFP cage is plain text",
    "numeric_mentions": [
      "2",
      "800G",
      "1.6T"
    ],
    "temporal_mentions": []
  },
  "relation_type": "VERA_RUBIN_NVL72_DUAL_800G_OSFP_PER_GPU"
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
platformVera Rubin04_knowledge_base/Vera Rubin
processorGPUGPU

⑤ V2 Draft(需要修正時直接編輯)

Inline repair

只編輯以下三個 Draft 區塊。完成後將 review_action 設為 REQUEST_REPAIR,再手動執行 Repair Preview。
執行腳本前,Draft 不會寫入 Claim Store 或 Graph。

V2 Atomic Claim Draft

但在 Vera Rubin NVL72 deployment 中,每顆 GPU 有 2 個 800G OSFP cages,因此每顆 GPU 合計 bandwidth 為 1.6T。

V2 Semantic Frame Draft

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/Vera Rubin",
        "label": "Vera Rubin"
      },
      "role": "platform"
    },
    {
      "node": {
        "id": "04_knowledge_base/GPU",
        "label": "GPU"
      },
      "role": "processor"
    }
  ],
  "qualifiers": {
    "condition_text": "OSFP cage is plain text",
    "numeric_mentions": [
      "2",
      "800G",
      "1.6T"
    ],
    "temporal_mentions": []
  },
  "relation_type": "VERA_RUBIN_NVL72_DUAL_800G_OSFP_PER_GPU"
}

V2 Revision Metadata Draft

{
  "epistemic_mode": "ASSERTED",
  "mapping_status": "COMPLETE"
}

⑥ 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 才是正式決策。