VR2-0789
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Groq LPU Decode Rack - Line hint:
999
Context Before
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.
With CPX being designed specifically for inference pre-fill, the LPU system is designed for inference decode given the LPU’s emphasis on higher bandwidth SRAM. 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, with the user paying much higher $/token to compensate for higher cost to serve.
Evidence
Context After
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
該系統設計為與 Nvidia GPUs 並列，後者負責較低 interactivity requests 的 decode。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"comparison_expression": "該系統設計為與 Nvidia GPUs 並列，後者負責較低 interactivity requests 的 decode。",
"entities": [
{
"id": "02_companies/NVDA",
"label": "Nvidia"
},
{
"id": "04_knowledge_base/GPU",
"label": "GPUs"
},
{
"id": "04_knowledge_base/Decode",
"label": "decode"
}
],
"frame_type": "COMPARISON",
"metric": "INTERACTIVITY",
"operator": "LESS_THAN",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [],
"temporal_mentions": []
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| comparison_entity_0 | Nvidia | NVDA |
| comparison_entity_1 | GPUs | GPU |
| comparison_entity_2 | decode | Decode |
⑤ 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 才是正式決策。