clm_3aabf39db46d4a9a836146b2f2d2a404_r1

NIEK2-0089

① SA Source

• Source: 開啟完整 SA 文章
• Section: SRAM and Memory Hierarchy
• Line hint: 73

Context Before

LPU 3’s near reticle size die layout is very similar to LPU 1. a significant amount of area taken is up by the 500MB of on-chip SRAM, with a very small amount of area dedicated to MatMul cores that offer 1.2 PFLOPs of FP8 compute – a fraction of compute compared to Nvidia GPUs. This compares to LPU 1 with 230MB of SRAM and 750 TFLOPs of INT8, with the performance increase mostly driven by node migration from GF16 to SF4. As a single monolithic die, advanced packaging isn’t required.

One of the benefits of relying on SF4 is that it isn’t constrained like TSMC’s N3, which is putting a cap on accelerator production and is a key reason why the industry remains compute constrained. ↗ This is in addition to not having HBM which is also constrained ↗. This allows Nvidia to ramp production of the LPU without sacrificing or eating into their valuable TSMC allocation or HBM allocations, representing true incremental revenue and capacity that noone else can access.

Evidence

Groq’s original plans for LPU Gen 4 was also with TSMC and Alchip as the back-end design partner

Context After

Source: Nvidia, SemiAnalysis Accelerator Model ↗

② Atomic Claim

Groq 原先的 LPU Gen 4 規劃同樣採用 TSMC，並由 Alchip 擔任後端設計合作夥伴。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "02_companies/Groq",
        "label": "Groq"
      },
      "role": "partner"
    },
    {
      "node": {
        "id": "04_knowledge_base/Groq LPU",
        "label": "LPU"
      },
      "role": "partner"
    },
    {
      "node": {
        "id": "02_companies/2330 台積電",
        "label": "TSMC"
      },
      "role": "partner"
    },
    {
      "node": {
        "id": "02_companies/3661",
        "label": "Alchip"
      },
      "role": "partner"
    }
  ],
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "4"
    ],
    "temporal_mentions": []
  },
  "relation_type": "PARTNERS_WITH"
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
partner	Groq	Groq
partner	LPU	04_knowledge_base/Groq LPU
partner	TSMC	02_companies/2330 台積電
partner	Alchip	3661

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