VR2-0271

① SA Source

Context Before

image

Source: Nvidia VR NVL72 BoM and Power Budget Model

Evidence

Firstly, the connection between the GPU and the ConnectX NICs evolved from GB200 to GB300 then to Vera Rubin

Context After

Essentially, this means ConnectX-8 has two hosts, Grace CPU and B300 GPU. This improves latency in the backend network. However, for VR NVL72, the direct connection between Rubin GPU and ConnectX-9 is reverted back to the same design as GB200, as Rubin does not have PCIe bandwidth for two Connect-9. Rubin connects to Vera via C2C link, then Vera will connect to ConnectX-9 via PCIe6 lanes.

Secondly, the local NVMe storage for Rubin has been moved to a different location from that of NVMe storage in Grace Blackwell. Previously, local NVMe storage was managed by BlueField-3. For VR NVL72, the local NVMe storage is physically on the Orchid module managed by the ConnectX-9.

② Atomic Claim

首先,GPU 與 ConnectX NICs 之間的連接方式,從 GB200GB300 再到 Vera Rubin 持續演進。

  • Epistemic Mode: ASSERTED
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/GPU",
        "label": "GPU"
      },
      "role": "endpoint_or_system"
    },
    {
      "node": {
        "id": "04_knowledge_base/GB200",
        "label": "GB200"
      },
      "role": "connected_entity"
    },
    {
      "node": {
        "id": "04_knowledge_base/GB300",
        "label": "GB300"
      },
      "role": "connected_entity"
    },
    {
      "node": {
        "id": "04_knowledge_base/Vera Rubin",
        "label": "Vera Rubin"
      },
      "role": "connected_entity"
    }
  ],
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "relation_type": "CONNECTS_TO"
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
endpoint_or_systemGPUGPU
connected_entityGB200GB200
connected_entityGB300GB300
connected_entityVera Rubin04_knowledge_base/Vera Rubin

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