VR2-0787

① SA Source

Context Before

Groq LPU Decode Rack

Since Nvidia acquired Groq entered into a licensing agreement for Groq’s technology and hired Groq’s key people December 2025, speculation has brewed on how exactly Nvidia will implement Groq’s technology. We believe that Nvidia will introduce a new LPU rack at GTC 2026. The LPU rack is designed to be used alongside Nvidia GPUs for inference.

Evidence

This comes at the expense of total throughput so this LPU decode system could be positioned at serving requests that require very high tokens per second per user

Context After

It will be designed to sit alongside Nvidia GPUs that handle decode for lower interactivity requests. We have shared more details of the system specification to Accelerator Model clients, where we highlight one part of the supply chain that could be a big beneficiary .

Some details we will share here is that there are 256 LPUs per rack and it is the 3rd generation Groq chip on Samsung 4nm (the 2nd generation is being skipped). We share an important supply chain detail that has an impact on growth and market share as well as topology in the Accelerator Model note.

② Atomic Claim

這會犧牲 total throughput,因此該 LPU decode system 可能定位於服務需要極高 tokens per second per user 的 requests。

  • Epistemic Mode: HYPOTHETICAL
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "attribute": "THROUGHPUT",
  "context_nodes": [
    {
      "id": "04_knowledge_base/Decode",
      "label": "decode"
    }
  ],
  "entity": {
    "id": "04_knowledge_base/Groq LPU",
    "label": "LPU"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "這會犧牲 total throughput,因此該 LPU decode system 可能定位於服務需要極高 tokens per second per user 的 requests。"
  }
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
entityLPU04_knowledge_base/Groq LPU
context_0decodeDecode

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