2025-08-12_scaling-the-memory-wall-the-rise-and-roadmap-of-hbm::HBM25-0026

① SA Source

Context Before

Within HBM itself there is undeveloped shoreline that can be unlocked from HBM4 onwards

The Revolutionary Changes Coming with HBM4

Evidence

HBM4 is where there will be more drastic changes to the HBM architecture on many facets: bus width, form factor and customization vs. “standard” off-the-shelf HBM.

Context After

HBM is high bandwidth because it has a much wider memory bus of 1024 bits compared to other forms of DRAM with 64 bits (16x the I/O). The bus of a single stack consists of multiple channels on each of the HBM core die. Currently, the bus for HBM3 and HBM3E is divided into sixteen 64-bit channels, with two nearly independent pseudo-channels per channel.

The big change for HBM4 is that the bus width will double to 2048-bit wide from the 1024-bit bus. Memory manufacturers will be relying more on the wider bus to drive up bandwidth rather than increasing pin speeds. JEDEC has said there is an initial agreement on speeds up to 6.4Gbps implying up to 1.6TB/s which is around 1.5x the bandwidth of HBM3E at peak speeds of 9.2Gbps. The wider bus will require more TSV area so the die size will increase 20% over the HBM 2E-3E size.

② Atomic Claim

HBM4 將在 bus width、form factor 與 customization 等面向帶來較大架構變化。

  • Epistemic Mode: EXPECTED
  • Mapping Status: COMPLETE

③ Semantic Frame

{
  "attribute": "architecture_change",
  "context_nodes": [],
  "entity": {
    "id": "04_knowledge_base/HBM4",
    "label": "HBM4"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "major changes in bus width, form factor, and customization"
  }
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
entityHBM4HBM4

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