VR2-0062

① SA Source

Context Before

Increasing clock speed 25% from 1.90GHz to 2.38GHz

Additionally, Nvidia claims up to an effective 50 PFLOPS of FP4 performance can be achieved with an updated 3rd generation Transformer Engine that replaces 2:4 structured sparsity from prior generations. We will detail this architectural feature for Rubin below.

Evidence

resulting in performance scaling only 1.6x of Blackwell

Context After

On the memory front, the move to HBM4 means double the bus width per stack, running at 10.8 GT/s for 22TB/s total bandwidth or 2.75x Blackwell at the same 288GB capacity as GB300. Memory bandwidth has been upgraded significantly from the original 13TB/s advertised at GTC 2025. In order to catch up to AMD MI450’s memory bandwidth, Nvidia requested much higher HBM4 pin speeds from the DRAM suppliers - well above the speeds that was in the JEDEC specification for HBM4.

While Nvidia is targeting 22TB/s, we understand that memory suppliers are having challenges hitting Nvidia’s requirements and we see it likely that initial shipments will come in slightly below at closer to 20TB/s. We have discussed the implications to SK Hynix, Samsung, and Micron extensively for Accelerator and HBM model subscribers. Micron is well behind Samsung and Hynix and we believe they are effectively out of the picture for Rubin HBM4. We have more details on qualifications and pin speeds in the Accelerator and HBM model

② Atomic Claim

Rubin 的 BF16TF32 效能相較 Blackwell 僅提升 1.6 倍。

  • Epistemic Mode: ASSERTED
  • Mapping Status: PARTIAL

③ Semantic Frame

{
  "comparison_expression": "Rubin 的 BF16/TF32 效能相較 Blackwell 僅提升 1.6 倍。",
  "entities": [
    {
      "id": "04_knowledge_base/BF16",
      "label": "BF16"
    },
    {
      "id": "04_knowledge_base/TF32",
      "label": "TF32"
    },
    {
      "id": "04_knowledge_base/Blackwell",
      "label": "Blackwell"
    }
  ],
  "frame_type": "COMPARISON",
  "metric": "COMPUTE_PERFORMANCE",
  "operator": "MULTIPLE_OF",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "1.6"
    ],
    "temporal_mentions": []
  }
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
comparison_entity_0BF16BF16
comparison_entity_1TF32TF32
comparison_entity_2BlackwellBlackwell

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