clm_fb6ca8fca6204ccf8a658e6957a7446a_r1

VR2-0728

① SA Source

• Source: 開啟完整 SA 文章
• Section: VR NVL72 TCO: BoM and Power Budget Analysis
• Line hint: 931

Context Before

Source: VR NVL72 Component BoM and Power Budget Model ↗

Evidence

The VR NVL72 is more expensive on a per-GPU capital cost basis, ~45% higher vs GB300s and ~14-15% higher vs the MI4XX given a higher server cost on a per GPU basis

Context After

However, one advantage for Nvidia’s VR SOCAMM option is that NVIDIA directly procures memory, allowing them to negotiate long-term agreements, volume-preferential terms with memory suppliers and most importantly, VVIP pricing. We think this will shield end customers from spikes in memory costs as we outline in our AI server apocalypse note ↗, and is another example of how, as the Central Bank of AI ↗, Nvidia is effectively hedging DRAM prices for all of its customers.

By contrast, AMD is much more exposed to DRAM price increases as it has about double the amount of DRAM, with about 55 TB per rack of LPDDR5 and 55 TB per rack of DDR5. For the AMD’s Helios rack scale system, AMD sells the GPU/board and does procure the LPDDR5 memory, but it does not procure DDR5 DRAM for rack compute trays; rack assemblers/ODMs source and integrate DDR5 memory. This leaves buyers of AMD’s racks more exposed because AMD is only able to potentially “hedge” the LPDDR5 portion via long-term contracts leaving the DDR5 portion completely exposed. Having double the DRAM content also nearly doubles the overall exposure.

② Atomic Claim

以每顆 GPU capital cost 計，VR NVL72 更昂貴，約比 GB300 高 45%，也比 MI4XX 高 14–15%，原因是每顆 GPU 對應的 server cost 較高。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "comparison_expression": "以每顆 GPU capital cost 計，VR NVL72 更昂貴，約比 GB300 高 45%，也比 MI4XX 高 14–15%，原因是每顆 GPU 對應的 server cost 較高。",
  "entities": [
    {
      "id": "04_knowledge_base/GPU",
      "label": "GPU"
    },
    {
      "id": "04_knowledge_base/VR NVL72",
      "label": "VR NVL72"
    },
    {
      "id": "04_knowledge_base/GB300",
      "label": "GB300"
    },
    {
      "id": "04_knowledge_base/MI400",
      "label": "MI4XX"
    }
  ],
  "frame_type": "COMPARISON",
  "metric": "COST",
  "operator": "GREATER_THAN",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "45%",
      "14–15%"
    ],
    "temporal_mentions": []
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
comparison_entity_0	GPU	GPU
comparison_entity_1	VR NVL72	04_knowledge_base/VR NVL72
comparison_entity_2	GB300	GB300
comparison_entity_3	MI4XX	MI400

⑤ 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 才是正式決策。