NIEK2-0049
① SA Source
- Source: 開啟完整 SA 文章
- Section:
LPU chip - Line hint:
49
Context Before
One of the selling points is that the chip can be manufactured and packaged entirely in the United States compared to their competitors being heavily reliant on the Asia semiconductor supply chain: logic and packaging in Taiwan, with HBM from Korea.
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.
Evidence
The follow on Groq LPU 2 was designed for Samsung Foundry’s SF4X node
Context After
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.
SRAM and Memory Hierarchy
② Atomic Claim
Groq LPU 2 原設計採用 Samsung Foundry 的 SF4X 製程。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/Groq LPU",
"label": "Groq LPU"
},
"role": "user_or_subject"
},
{
"node": {
"id": "02_companies/005930",
"label": "Samsung Foundry"
},
"role": "used_entity"
},
{
"node": {
"id": "04_knowledge_base/SF4X",
"label": "SF4X"
},
"role": "used_entity"
}
],
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"2"
],
"temporal_mentions": []
},
"relation_type": "USES"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| user_or_subject | Groq LPU | 04_knowledge_base/Groq LPU |
| used_entity | Samsung Foundry | 005930 |
| used_entity | SF4X | SF4X |
⑤ 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 才是正式決策。