VR2-0624
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Connecting GPUs in the Scale-Out InfiniBand Network - Line hint:
745
Context Before
Connecting GPUs in the Scale-Out InfiniBand Network
Broadly, there are three flavors of scale-out deployments for Vera Rubin NVL72. We have InfiniBand-based clusters which employ the NVIDIA Quantum series of switches, NVIDIA Ethernet-based clusters employing Spectrum series switches and lastly, non-Nvidia Ethernet such as Tomahawk-based, Cisco Silicon One or Teralynx-based Ethernet switches. Some Ethernet-based clusters deployed by hyperscalers will use AECs for NIC-to-TOR and switch-to-switch connections, while other Ethernet-based clusters using only optical interconnects will usually adopt a multi-plane and multi-rail networking architecture. What is particularly noteworthy about Vera Rubin NVL72 deployments, however, is that it is the first Nvidia GPU generation where we will be seeing some Co-Packaged-Optics (CPO) deployments in the scale-out backend network.
Evidence
While there are both InfiniBand and Spectrum-X based clusters, the InfiniBand-based Quantum X800-34XX series of switches is more popular with Neoclouds than with hyperscalers. For InfiniBand, there are two deployment types – the first is the Quantum X800-Q3400 with pluggable optics and the second is the Quantum X800-Q3450 CPO-based switch that use co-packaged Optical Engines (OE) instead of pluggable transceivers.
Context After
The Quantum X800-Q3400 is logically a multi-plane switch combining 4 Quantum-3 ASICs into a single switch box, though we will dive into this equivalence later in the article. This multi-plane “topology” is abstracted away and as far as network engineers are concerned, the Q3400 is a single switch with 144 ports – or a “little boy” switch.
② Atomic Claim
雖然同時有 InfiniBand 與 Spectrum-X cluster，但 InfiniBand-based Quantum X800-34XX series switches 在 Neoclouds 中比在 hyperscalers 中更普遍。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "SCALABILITY",
"context_nodes": [
{
"id": "04_knowledge_base/Quantum X800",
"label": "Quantum X800-34XX series"
},
{
"id": "03_industries/Neocloud產業",
"label": "Neoclouds"
},
{
"id": "04_knowledge_base/Hyperscaler",
"label": "hyperscalers"
}
],
"entity": {
"id": "04_knowledge_base/InfiniBand",
"label": "InfiniBand"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"34X"
],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"34X"
],
"value_text": "雖然同時有 InfiniBand 與 Spectrum-X cluster，但 InfiniBand-based Quantum X800-34XX series switches 在 Neoclouds 中比在 hyperscalers 中更普遍。"
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | InfiniBand | InfiniBand |
| context_0 | Quantum X800-34XX series | 04_knowledge_base/Quantum X800 |
| context_1 | Neoclouds | 03_industries/Neocloud產業 |
| context_2 | hyperscalers | Hyperscaler |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
雖然同時有 InfiniBand 與 Spectrum-X cluster，但 InfiniBand-based Quantum X800-34XX series switches 在 Neoclouds 中比在 hyperscalers 中更普遍。
V2 Semantic Frame Draft
{
"attribute": "SCALABILITY",
"context_nodes": [
{
"id": "04_knowledge_base/Quantum X800",
"label": "Quantum X800-34XX series"
},
{
"id": "03_industries/Neocloud產業",
"label": "Neoclouds"
},
{
"id": "04_knowledge_base/Hyperscaler",
"label": "hyperscalers"
}
],
"entity": {
"id": "04_knowledge_base/InfiniBand",
"label": "InfiniBand"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"34X"
],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"34X"
],
"value_text": "雖然同時有 InfiniBand 與 Spectrum-X cluster，但 InfiniBand-based Quantum X800-34XX series switches 在 Neoclouds 中比在 hyperscalers 中更普遍。"
}
}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 才是正式決策。