VR2R-0744
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Groq LPU Decode Rack - Line hint:
997
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
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.
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
若 LPU decode system 定位於極高 tokens-per-second-per-user 的服務，使用者可能支付更高 $/token，以補償較高 serving cost。
- Epistemic Mode:
HYPOTHETICAL - Mapping Status:
PARTIAL
③ Semantic Frame
{
"frame_type": "CLAIM_ONLY",
"qualifiers": {
"condition_text": "continuation of the LPU high-tokens-per-second-per-user positioning; Possible high-interactivity LPU service positioning and higher serving cost",
"numeric_mentions": [],
"temporal_mentions": []
},
"reason": "CONTINUATION_FRAGMENT_WITHOUT_EXPLICIT_CANONICAL_SUBJECT",
"statement": "若 [[04_knowledge_base/Groq LPU|LPU]] [[04_knowledge_base/Decode|decode]] system 定位於極高 tokens-per-second-per-user 的服務，使用者可能支付更高 $/token，以補償較高 serving cost。"
}④ Canonical Entity Mapping
- 此
CLAIM_ONLYrevision 沒有 canonical Entity mapping。
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
若 LPU decode system 定位於極高 tokens-per-second-per-user 的服務，使用者可能支付更高 $/token，以補償較高 serving cost。
V2 Semantic Frame Draft
{
"frame_type": "CLAIM_ONLY",
"qualifiers": {
"condition_text": "continuation of the LPU high-tokens-per-second-per-user positioning; Possible high-interactivity LPU service positioning and higher serving cost",
"numeric_mentions": [],
"temporal_mentions": []
},
"reason": "CONTINUATION_FRAGMENT_WITHOUT_EXPLICIT_CANONICAL_SUBJECT",
"statement": "若 [[04_knowledge_base/Groq LPU|LPU]] [[04_knowledge_base/Decode|decode]] system 定位於極高 tokens-per-second-per-user 的服務，使用者可能支付更高 $/token，以補償較高 serving cost。"
}V2 Revision Metadata Draft
{
"epistemic_mode": "HYPOTHETICAL",
"mapping_status": "PARTIAL"
}⑥ 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 才是正式決策。