IX2-0605

① SA Source

  • Source: 開啟完整 SA 文章
  • Section: Total Cost of Ownership (NVL72, Blackwell, Blackwell Ultra, MI355, Hopper, MI325, MI300)
  • Line hint: 824

Context Before

Total Cost of Ownership (NVL72, Blackwell, Blackwell Ultra, MI355, Hopper, MI325, MI300)

Looking at capital costs across comparable generations, Nvidia systems tend to have higher capital cost than AMD systems. This is driven mostly by higher compute tray content which is driven by higher GPU pricing – it is well known from their financials that Nvidia enjoys higher margins on their GPUs than other vendors. As an example, MI300X compute tray content sits at ~170K for H100 SXM, and the gap widens further in later generations. MI355X is at ~264K and B300 to ~$344K. That incremental silicon content flows directly into higher server cost, and ultimately higher all-in cluster capex per server.

Evidence

This similar dynamic carries over into the Blackwell generation, where an increase in GPU content drives rising total Server cost, in turn driving higher total upfront cluster capex per server, resulting in higher capital cost of ownership

Context After

image

Source: SemiAnalysis AI TCO Model

② Atomic Claim

Blackwell 世代也呈現類似動態:GPU content 增加推升整體 Server cost,再進一步提高每台 server 的 upfront cluster capex 與 capital cost of ownership。

  • Epistemic Mode: ASSERTED
  • Mapping Status: PARTIAL

③ Semantic Frame

{
  "attribute": "COST",
  "context_nodes": [
    {
      "id": "04_knowledge_base/GPU",
      "label": "GPU"
    }
  ],
  "entity": {
    "id": "04_knowledge_base/Blackwell",
    "label": "Blackwell"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "Blackwell 世代也呈現類似動態:GPU content 增加推升整體 Server cost,再進一步提高每台 server 的 upfront cluster capex 與 capital cost of ownership。"
  }
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
entityBlackwellBlackwell
context_0GPUGPU

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