VR2-0761

① SA Source

Context Before

image

Source: SemiAnalysis AI TCO Model

Evidence

VR has a higher TCO per GPU compared to MI4XX, yet VR marketed PFLOPs are lower vs MI4XX resulting in a TCO per PFLOP disadvantage for the VR vs MI4XX

Context After

NVIDIA is offering sparsity for FP4, marketing 50 PFLOPS of FP4, while AMD has opsted to remove sparsity support since CDNA4 for inference dtypes. Harnessing the 50 PFLOPS sparse vs 35 PFLOPS dense drops the cost per perf in units of $/hr per Marketed PFLOP by 35% – a valid comparison if AI Labs can indeed successfully harness Sparse FP4 on the VR NVL72.

As always, one caveat is that this comparison is done based on a marketed dense PFLOP basis. Effective dense PFLOP (i.e. the real world chip throughput) can differ based on Model Flops Utilization % (MFU), and in general we have seen NVIDIA chip operate at a higher MFU % vs AMD chips, suggesting that performance per TCO based on effective dense PFLOPs could be better for NVIDIA systems vs AMD – however, MFU is dependent on actual workloads with no one-size-fits-all MFU % that is consistently applicable to either systems.

② Atomic Claim

VR 每顆 GPU TCO 高於 MI4XX,但 VR 行銷 PFLOPs 又低於 MI4XX,因此 VR 相較 MI4XX 的 TCO per PFLOP 處於劣勢。

  • Epistemic Mode: ASSERTED
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "comparison_expression": "VR 每顆 GPU TCO 高於 MI4XX,但 VR 行銷 PFLOPs 又低於 MI4XX,因此 VR 相較 MI4XX 的 TCO per PFLOP 處於劣勢。",
  "entities": [
    {
      "id": "04_knowledge_base/GPU",
      "label": "GPU"
    },
    {
      "id": "04_knowledge_base/MI400",
      "label": "MI4XX"
    }
  ],
  "frame_type": "COMPARISON",
  "metric": "COMPUTE_PERFORMANCE",
  "operator": "GREATER_THAN",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  }
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
comparison_entity_0GPUGPU
comparison_entity_1MI4XXMI400

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