VR2R-0571::SPLIT02
① SA Source
- Source: 開啟完整 SA 文章
- Section:
GB200 Hardware Architecture - Component Supply Chain & BOM - Line hint:
733
Context Before
Vera Rubin NVL72 Scale-up Topology. Source: SemiAnalysis AI Networking Model ↗
While the VR NVL72 system features GPUs and scale-up switches that are connected by copper cables, the VR HGX system features servers consisting of eight Rubin GPUs and four NVLink Switch chips. The second meaningful difference between the NVL72 and HGX deployments is that the former has a scale-out bandwidth of 1.6T per GPU while the latter only has a scale-out bandwidth of 800G per GPU. How is it that all Rubin 200 deployments use CX-9 NICs even though some deployments have half the per GPU scale-out bandwidth?
Evidence
The HGX Rubin NVL8 server consists of eight 800G CX-9 NIC packages – one NIC per GPU – which means that the scale-out bandwidth does not increase from its predecessor, the HGX B300 server. The Vera Rubin NVL72 deployment on the other hand doubles the per GPU scale-out bandwidth to 1.6T, but not by doubling the bandwidth per NIC. Rather, the “1.6T NIC” attached to each Rubin chip is comprised of two 800G CX-9 packages that is connected to the Vera CPU by PCIe Gen 6.0 lanes.
Context After
Each compute tray on the VR NVL72 has eight 800G CX-9 NICs, but there are two possibilities for the number of OSFP cages - either one 1.6T OSFP cage per GPU for a total of 4 per compute tray, or two 800G OSFP cages per GPU for a total of 8 cages per compute tray. We think that the latter would be the more popular deployment assumption, and will be the base case for our discussion of scale-out networking architectures in later sections of the article.
② Atomic Claim
HGX Rubin NVL8 does not increase scale-out bandwidth over HGX B300.
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "SCALE_OUT_COMPARISON",
"context_nodes": [
{
"id": "04_knowledge_base/Vera Rubin",
"label": "Rubin"
},
{
"id": "04_knowledge_base/NVL8",
"label": "NVL8"
},
{
"id": "04_knowledge_base/NVIDIA B300",
"label": "B300"
}
],
"entity": {
"id": "04_knowledge_base/HGX",
"label": "HGX"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "HGX Rubin NVL8 does not increase scale-out bandwidth over HGX B300."
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | HGX | HGX |
| context_0 | Rubin | 04_knowledge_base/Vera Rubin |
| context_1 | NVL8 | NVL8 |
| context_2 | B300 | 04_knowledge_base/NVIDIA B300 |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
HGX Rubin NVL8 does not increase scale-out bandwidth over HGX B300.
V2 Semantic Frame Draft
{
"attribute": "SCALE_OUT_COMPARISON",
"context_nodes": [
{
"id": "04_knowledge_base/Vera Rubin",
"label": "Rubin"
},
{
"id": "04_knowledge_base/NVL8",
"label": "NVL8"
},
{
"id": "04_knowledge_base/NVIDIA B300",
"label": "B300"
}
],
"entity": {
"id": "04_knowledge_base/HGX",
"label": "HGX"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "HGX Rubin NVL8 does not increase scale-out bandwidth over HGX B300."
}
}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 才是正式決策。