NIEK2-0021

① SA Source

Context Before

Let’s now go through a refresher on the LPU architecture to see how Groq’s LPU complements Nvidia’s GPU. For more details see our original Groq piece. The premise from that piece remains unchanged: the standalone Groq LPU system is not economical for serving tokens at scale, but it can serve tokens very quickly which can demand a large market premium. This is the premise behind how LPU fits into a disaggregated decode system.

LPU chip

Evidence

Groq’s first and only publicly announced LPU architecture was detailed in their ISCA 2020 paper

Context After

Concretely, LPU architecture has VXM slices for vector operations, MEM slices for loading/storing data, SXM slices for tensor shape manipulation, and MXM slices for performing matrix multiplication. Spatially, the slices are laid out horizontally, allowing the data to stream horizontally. Within a slice, instructions are pumped vertically across units. Conceptually, LPU resembles a systolic array that pumps instructions vertically and data horizontally.

image

② Atomic Claim

Groq 第一代、也是目前唯一公開發表的 LPU 架構,已在其 ISCA 2020 論文中詳述。

  • Epistemic Mode: ASSERTED
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "additional_nodes": [],
  "frame_type": "RELATION",
  "object": {
    "id": "04_knowledge_base/Groq LPU",
    "label": "LPU"
  },
  "predicate": "INTRODUCES",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "2020"
    ],
    "temporal_mentions": [
      "2020"
    ]
  },
  "subject": {
    "id": "02_companies/Groq",
    "label": "Groq"
  }
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
subjectGroqGroq
objectLPU04_knowledge_base/Groq LPU

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