2025-06-13_amd-advancing-ai-mi350x-and-mi400-ualoe72-mi500-ual256::AMD25-0030
① SA Source
- Source: 開啟完整 SA 文章
- Section:
MI350X, MI355X, MI400 Series UALoE72 Bill Of Materials and Total Cost of Ownership - Line hint:
477
Context Before
Source: SemiAnalysis TCO model
Evidence
When it comes to performance per TCO, the MI400 delivers better performance per TCO in terms of Memory Bandwidth as well as PFLOPS for FP4 Dense, FP6 Dense and FP8 Dense than the VR200 NVL144 regardless of the networking solution employed for the VR200. However, its much higher power draw per GPU package means that it delivers slightly less TFLOPS per Watt compared to the VR200 NVL144.
Context After
Source: Semianalysis TCO model
② Atomic Claim
SemiAnalysis 估計 MI400 在 memory-bandwidth 與 FP4/FP6/FP8 dense PFLOPS 的 perf/TCO 優於 VR200 NVL144，但 TFLOPS/W 略低。
- Epistemic Mode:
ESTIMATED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"comparison_expression": "MI400 better perf/TCO on memory bandwidth and dense FP4/FP6/FP8; slightly lower TFLOPS/W",
"entities": [
{
"id": "04_knowledge_base/MI400",
"label": "MI400"
},
{
"id": "04_knowledge_base/VR200",
"label": "VR200"
},
{
"id": "04_knowledge_base/NVL144",
"label": "NVL144"
},
{
"id": "04_knowledge_base/FP4",
"label": "FP4"
},
{
"id": "04_knowledge_base/FP6",
"label": "FP6"
},
{
"id": "04_knowledge_base/FP8",
"label": "FP8"
}
],
"frame_type": "COMPARISON",
"metric": "performance_per_tco_and_efficiency",
"operator": "MIXED",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| comparison_entity_0 | MI400 | MI400 |
| comparison_entity_1 | VR200 | VR200 |
| comparison_entity_2 | NVL144 | NVL144 |
| comparison_entity_3 | FP4 | FP4 |
| comparison_entity_4 | FP6 | FP6 |
| comparison_entity_5 | FP8 | FP8 |
⑤ 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 才是正式決策。