VR-COV-VR-CPO-68-total-3
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Ethernet-Based Cluster Deployments - Line hint:
829
Context Before
What advantages do CPO switches such as the SN6800 deliver for Neoclouds like Coreweave and Lambda when it comes to large-scale cluster deployments?
As discussed in our recent deep dive article on co-packaged optics, ↗ the first reason is that a significant amount of power can be saved by eliminating most of the transceiver content. If we compare the power consumption of one 800G DR4 optical transceiver (16-17W) to the power required by optical engines (OEs) and external light source (ELS) modules to delivery an equivalent 800G of bandwidth in the scale-out network, we see an average ~70% reduction in power used for optical transceivers. Taking a step back, this would translate to 10% in savings for the total networking equipment power consumption in a 3-Layer HGX Rubin NVL8 cluster. This reduction in networking equipment power consumption is however relatively insignificant and amounts to only ~1% of total cluster power consumption because the server’s power budget dominates the equation.
Evidence
Context After
Source: Nvidia VR NVL72 Component BoM and Power Budget Model ↗
The second benefit is a reduction in cost stemming from eliminating almost all transceivers. There is even more room for price reduction if we are looking at NVIDIA LinkX transceivers, which tend to be priced at significant premium to their generic equivalent. If we compare total networking costs for a 3-Layer network with and without CPO-based switches in the scale-out domain, we see an average of ~75% reduction in transceiver costs. However, as with the power savings above, such costs savings tend not to move the needle dramatically considering the full cluster costs.
② Atomic Claim
The February Rubin NVL8 HGX neocloud InfiniBand model estimates total power changes by -1% with CPO versus non-CPO in its 3-layer network scenario.
- Epistemic Mode:
ESTIMATED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "HGX_MODEL_POWER_CHANGE",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/CPO",
"label": "CPO"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "total; 3 layers; -1%"
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | CPO | CPO |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
The February Rubin NVL8 HGX neocloud InfiniBand model estimates total power changes by -1% with CPO versus non-CPO in its 3-layer network scenario.
V2 Semantic Frame Draft
{
"attribute": "HGX_MODEL_POWER_CHANGE",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/CPO",
"label": "CPO"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "total; 3 layers; -1%"
}
}V2 Revision Metadata Draft
{
"epistemic_mode": "ESTIMATED",
"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 才是正式決策。