VR2R-0596
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Connecting GPUs in the Scale-Out InfiniBand Network - Line hint:
763
Context Before
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:
2(k2)L
Evidence
Context After
2(115,2001,6002)3=2(722)3=93,312
By one 1.6T logical port, we mean that the two 800G OSFP cages connected to each GPU are connected to a single, dual-port 1.6T transceiver at the leaf layer because the two 800G ports are effectively performing the function of one 1.6T port – and hence the term “logical”.
② Atomic Claim
在原文所述假設情境中，1-plane、3-layer network 若使用單一 1.6T logical port，maximum cluster size 僅為 93,312 顆 GPUs。
- Epistemic Mode:
HYPOTHETICAL - Mapping Status:
PARTIAL
③ Semantic Frame
{
"attribute": "MAX_CLUSTER_SIZE_UNDER_1P_3L_1_6T_TOPOLOGY",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/GPU",
"label": "GPU"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": "illustrative network topology; Explicit hypothetical illustration: one plane, three layers, one 1.6T logical port",
"numeric_mentions": [
"1-plane",
"3-layer",
"1.6T",
"93,312"
],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"1-plane",
"3-layer",
"1.6T",
"93,312"
],
"value_text": "maximum cluster size is 93,312 GPUs."
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | GPU | GPU |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
在原文所述假設情境中，1-plane、3-layer network 若使用單一 1.6T logical port，maximum cluster size 僅為 93,312 顆 GPUs。
V2 Semantic Frame Draft
{
"attribute": "MAX_CLUSTER_SIZE_UNDER_1P_3L_1_6T_TOPOLOGY",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/GPU",
"label": "GPU"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": "illustrative network topology; Explicit hypothetical illustration: one plane, three layers, one 1.6T logical port",
"numeric_mentions": [
"1-plane",
"3-layer",
"1.6T",
"93,312"
],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"1-plane",
"3-layer",
"1.6T",
"93,312"
],
"value_text": "maximum cluster size is 93,312 GPUs."
}
}V2 Revision Metadata Draft
{
"epistemic_mode": "HYPOTHETICAL",
"mapping_status": "PARTIAL"
}⑥ 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 才是正式決策。