SA260324R-0054
① SA Source
- Source: 開啟完整 SA 文章
- Section:
LPU chip - Line hint:
51
Context Before
Since then, Groq’s roadmap has stalled due to execution, with no LPU 2 having been shipped. This leaves the Groq LPU looking even more dated against competing roadmaps. What was once a meaningful but still manageable node disadvantage versus 7nm-era peers has widened into a far sharper gap, with all leading accelerator platforms now moving onto 3nm-class processes in 2026.
The follow on Groq LPU 2 was designed for Samsung Foundry’s SF4X node, specifically at Samsung’s Austin fab, allowing them to extend the pitch that Groq is fabricated domestically in the USA. Samsung would also provide support for the back-end design. The choice of Samsung was driven by favorable terms / investment, with Samsung Foundry struggling to find customers for its advanced nodes and missing out on an AI logic customer. Unsurprisingly, Samsung was a key investor in Groq’s subsequent Series D in August 2024, and most recently in September 2025 before the Nvidia “acquisition.”
Evidence
However, the Groq LPU 2 was never productized because of design issues. The C2C SerDes on the chip couldn’t hit the advertised 112G speed which caused the design to malfunction, as we detailed long ago in the Accelerator model ↗. The third generation Groq LPU is the one that Nvidia will be productizing.
Context After
SRAM and Memory Hierarchy
We have written about the role of SRAM in the memory hierarchy, but the quick recap is that SRAM is very fast (low latency and high bandwidth) but this comes at the expense of density and therefore cost.
② Atomic Claim
不過，Groq LPU 2 因設計問題，最終從未產品化。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "GEN2_PRODUCTIZATION_STATUS",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/Groq LPU",
"label": "Groq LPU"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": "because of design issues",
"numeric_mentions": [
"2"
],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"2"
],
"value_text": "LPU 2 因設計問題從未產品化"
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | Groq LPU | 04_knowledge_base/Groq LPU |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
不過，Groq LPU 2 因設計問題，最終從未產品化。
V2 Semantic Frame Draft
{
"attribute": "GEN2_PRODUCTIZATION_STATUS",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/Groq LPU",
"label": "Groq LPU"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": "because of design issues",
"numeric_mentions": [
"2"
],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [
"2"
],
"value_text": "LPU 2 因設計問題從未產品化"
}
}V2 Revision Metadata Draft
{
"epistemic_mode": "ASSERTED",
"mapping_status": "COMPLETE"
}⑥ 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 才是正式決策。