clm_bf7c4db4888d4583acb570b6888b6071_r1

2025-06-13_amd-advancing-ai-mi350x-and-mi400-ualoe72-mi500-ual256::AMD25-0002

① SA Source

• Source: 開啟完整 SA 文章
• Section: AMD Advancing AI: MI350X and MI400 UALoE72, MI500 UAL256
• Line hint: 17

Context Before

---

id: 174558644
title: “AMD Advancing AI: MI350X and MI400 UALoE72, MI500 UAL256”
subtitle: “Software Improvement, Marketing RDFs, AMD Fostering Neocloud, MI355 is not Rack Scale, MI400 is UALoE, Not UALink”
published_at: “2025-06-13T15:38:21.000Z”
authors: [“Kimbo Chen”, “Dylan Patel”, “Daniel Nishball”, “Wega Chu”, “Ivan Chiam”, “Gerald Wong”, “Patrick Zhou”]
url: “https://newsletter.semianalysis.com/p/amd-advancing-ai-mi350x-and-mi400-ualoe72-mi500-ual256”
audience: “only_paid”
access: authenticated_subscription
assets: local-v2
source_selector: “.available-content”
collected_at: “2026-08-08T13:34:24.629331+00:00”

AMD Advancing AI: MI350X and MI400 UALoE72, MI500 UAL256

Evidence

Notwithstanding the reality distortion field projected by AMD, the MI355X is not a rack scale product, and it is not competitive against Nvidia’s GB200 NVL72 at frontier model inference or training.

Context After

Instead, it is the MI400 Series that is a true rack scale solution that could potentially be competitive with Nvidia’s VR200 NVL144 rack scale solutions in H2 2026. There is also some marketing spin around the MI400 Series as AMD has renamed its “IF over Ethernet” protocol to “UALink Protocol over Ethernet”, which is not real UALink.

In this article, we will discuss the relative competitiveness of AMD’s new products and analyze their total cost of ownership. We will also elaborate on AMD’s new hyperscale customer, AWS, and on the flip side, the continued disappointment in follow-on orders on from existing customer Microsoft.

② Atomic Claim

SemiAnalysis 判斷 MI355X 不是 rack-scale product，且在 frontier inference/training 不具 GB200 NVL72 競爭力。

• Epistemic Mode: INFERRED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "comparison_expression": "MI355X not rack scale and not competitive vs GB200 NVL72",
  "entities": [
    {
      "id": "04_knowledge_base/MI355X",
      "label": "MI355X"
    },
    {
      "id": "04_knowledge_base/GB200 NVL72",
      "label": "GB200 NVL72"
    }
  ],
  "frame_type": "COMPARISON",
  "metric": "frontier_inference_training_competitiveness",
  "operator": "MI355X_LOWER",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
comparison_entity_0	MI355X	MI355X
comparison_entity_1	GB200 NVL72	04_knowledge_base/GB200 NVL72

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