clm_7bb3e619167349fabf8b3afe5671ae7f_r1

VR2-0218

① SA Source

• Source: 開啟完整 SA 文章
• Section: BlueField-4
• Line hint: 319

Context Before

Source: Nvidia VR NVL72 BoM and Power Budget Model ↗

Evidence

However, just like BlueField-3, BlueField-4 will only be adopted by a handful of customers, namely CoreWeave and other smaller Neoclouds customers who have less customization capability

Context After

Speaking of BlueField-4, it is important to discuss the new offering Jensen highlighted at CES earlier this year: ICMS, or Inference Context Memory Storage — a platform that we hear may be rebranded to “CMX” at GTC. ICMS, or CMX, introduces a third, entirely separate network dedicated solely to context memory. CMX is a purpose-built KV cache fabric. As long-context inference pushes context windows toward millions of tokens and agentic concurrency scales across users and services, the current memory hierarchy used to store KVcache begins to look insufficient.

KV cache grows linearly with sequence length and multiplicatively with workload parallelism, quickly expanding beyond what any single tier of memory was designed to hold. GPU HBM, while unmatched in bandwidth and latency, is not enough on its own to store KV especially for longer sequence length queries that are becoming popular between turns or tool calls. Host DRAM extends capacity but remains node-bound and limited in aggregate footprint and ultimately has limited capacity. Meanwhile, traditional shared storage—architected for durability rather than latency —has more access time and power overhead, making it unsuitable for participation in the decode loop.

② Atomic Claim

與 BlueField-3 類似，BlueField-4 預期只會被少數客戶採用，例如 CoreWeave 與其他 customization 能力較低的小型 Neoclouds 客戶。

• Epistemic Mode: EXPECTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "comparison_expression": "與 BlueField-3 類似，BlueField-4 預期只會被少數客戶採用，例如 CoreWeave 與其他 customization 能力較低的小型 Neoclouds 客戶。",
  "entities": [
    {
      "id": "04_knowledge_base/BlueField-3",
      "label": "BlueField-3"
    },
    {
      "id": "04_knowledge_base/BlueField-4",
      "label": "BlueField-4"
    },
    {
      "id": "02_companies/CRWV",
      "label": "CoreWeave"
    },
    {
      "id": "03_industries/Neocloud產業",
      "label": "Neoclouds"
    }
  ],
  "frame_type": "COMPARISON",
  "metric": "ADOPTION_STATUS",
  "operator": "LESS_THAN",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "3",
      "4"
    ],
    "temporal_mentions": []
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
comparison_entity_0	BlueField-3	BlueField-3
comparison_entity_1	BlueField-4	BlueField-4
comparison_entity_2	CoreWeave	CRWV
comparison_entity_3	Neoclouds	03_industries/Neocloud產業

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