AI-Infra 组:AI 算力厂商落地实践市场研究(组概述与横向对比)
1. 组概述
1.1. 研究范围
本组(03-市场研究 / 06-AI-Infra 组)对 2026 年 AI 算力产业中最具代表性的 10 个平台/生态逐一进行市场研究,聚焦「具体厂商落地实践」——即:这些算力平台真实卖给了谁、部署规模多大、跑出了什么成绩、支撑上层智能体负载的能力如何。
覆盖三类研究对象:
- 国际头部与追赶者:NVIDIA(GB200 NVL72 + CUDA 全栈)、AMD(MI355X + ROCm)、Google TPU(Ironwood)、AWS Trainium/Inferentia(Project Rainier);
- 国产头部与二线:华为昇腾(CloudMatrix 384 + CANN 全栈)、寒武纪(思元系列)、摩尔线程(MTT S5000 + 夸娥集群)、海光信息/天数智芯/燧原科技(整合篇);
- 开源软件生态:推理 serving 生态(vLLM/SGLang/TensorRT-LLM/MindIE)与训练框架生态(Megatron-LM/DeepSpeed/FSDP/Colossal-AI)。
每个平台一篇独立文档(详见第 6 节文档导航),统一套用八段结构:介绍、名词解释、功能说明与产品线、平台架构、Harness 设计(六层逐层剖析)、实际案例、总结、参考资料。
1.2. 与 02-行业赋能/01-AI-Infra 组的分工说明
本组与 02-行业赋能/01-AI-Infra 组存在明确的分工边界:
| 维度 | 02-行业赋能 / 01-AI-Infra 组 | 本组(03-市场研究 / 06-AI-Infra 组) |
|---|---|---|
| 研究对象 | 通用技术栈:AI 芯片(GPU/NPU)→ 服务器与超节点 → 集群互联与机房 → 训推框架与调度的技术体系本身 | 具体厂商:上述技术栈在各厂商的产品化落地与商业实践 |
| 核心问题 | 「这类技术是怎么工作的」 | 「这家厂商做得怎么样、卖给谁、可信度如何」 |
| 内容形态 | 方向类文档(含 AGENTS.md / SKILL.md 规范) | 市场研究文档(八段结构 + 六层评级 + 案例矩阵) |
| 交叉处理 | 两边涉及同一技术概念(如超节点、PD 分离)时,技术原理归行业赋能组,厂商口径与案例归本组 | 同左 |
1.3. 分析框架与评级口径
全部平台统一套用项目参数卡定义的 Harness 六层能力模型:
| 层 | 名称 | 职责 |
|---|---|---|
| L1 | 上下文工程层 | 决定模型「看到什么」:检索、压缩、缓存、优先级排序(KV Cache 复用属此层) |
| L2 | 工具与执行层 | 决定模型「能做什么」:工具注册、沙箱、调度(推理引擎的 OpenAI 兼容 API、Function Call 属此层) |
| L3 | 编排与控制层 | 决定「按什么顺序做」:规划、状态机、调度编排(并行策略编排、PD 分离调度属此层) |
| L4 | 记忆与状态层 | 决定「记住什么」:会话态、检查点(KV 持久化、训练 checkpoint 属此层) |
| L5 | 评估与观测层 | 决定「做得好不好」:指标、回归集(MFU、TTFT/TPOT、集群可观测属此层) |
| L6 | 治理与安全层 | 决定「不能做什么」:权限、审计、合规(信创合规、精度治理、企业支持属此层) |
评级口径(四级):强(原生一等公民机制,可配置可扩展)/ 中强(有原生机制但覆盖不完整)/ 中(需用户自行组合,或仅提供基础原语)/ 弱(基本缺失,需外部系统补齐)。「弱(不透明)」表示公开可查证机制缺失(不等于产品实际能力缺失)。
必须强调的方法论声明:本组所有六层评级均为基于公开资料的定性判断,非统一基准实测。算力平台之间不存在统一的智能体负载基准;性能数据多为厂商口径(本组反复标注),第三方可验证数据仅 NVIDIA(MLPerf 体系完整提交)、Google TPU(MLPerf 部分提交)与 AWS/AMD 的零星提交。评级反映「公开可查证机制与证据的密度与深度」,不等于「生产环境实测表现」。
1.4. 产业格局:芯片、超节点、集群、框架四层
图 0-1|AI Infra 产业格局与本组 10 平台的位置(四层视角)
示意:基于本组 10 篇研究综合绘制;出货份额为 IDC 2025 口径(经腾讯云社区转述)。
1.5. 2025—2026 年关键事件时间线
以下事件直接塑造了本组 10 个平台的竞争格局,各篇文档均有对应展开:
| 时间 | 事件 | 影响 |
|---|---|---|
| 2024-03 | NVIDIA GTC 发布 GB200 NVL72 | 超节点成为竞争的基本单位 |
| 2025-04 | 华为云生态大会发布 CloudMatrix 384,芜湖规模上线 | 国产阵营给出「系统级规模补单卡差距」的答案 |
| 2025-04 | Google Cloud Next 25 发布 Ironwood(第 7 代 TPU),提出「推论时代」叙事 | 行业重心从训练转向推理侧服务 |
| 2025-05 | vLLM 与 DeepSpeed 同批加入 PyTorch 基金会 | 开源训推基础设施的中立治理成型 |
| 2025-06 | AMD Advancing AI 发布 MI350 系列与 ROCm 7、预告 Helios | 开放标准路线正式对位 NVLink 闭环 |
| 2025-06 | GB300 NVL72(Blackwell Ultra)客户出货 | MLPerf Inference v5.1 首秀刷新全部新增基准 |
| 2025-09 | 昇腾产业峰会:超节点累计 300 套、邮储银行大 EP 实践;全联接大会公布 950/960/970 路线图 | 华为首次以年度节奏公开三年芯片路线 |
| 2025-09 | TensorRT-LLM v1.0(PyTorch-first + trtllm-serve) | 推理引擎易用性门槛大幅下降 |
| 2025-11 | Project Rainier 上线(近 50 万颗 Trainium2) | 云厂商自研芯片规模化外供的里程碑 |
| 2025-11 | Ironwood GA 公告;Anthropic 百万颗 TPU 承诺推进 | TPU 从自用走向头部客户主力供给 |
| 2025-12 | 摩尔线程科创板上市(「国产 GPU 第一股」);AWS re:Invent 发布 Trainium3 | 国产 GPU 资本化与国际代际推进并行 |
| 2026-03 | 寒武纪 2025 年报:首次年度盈利、首次分红、摘「U」 | 国产 AI 芯片商业模式验证完成 |
| 2026-09-11 | 燧原科技科创板上市(688801) | 「国产 GPU 四小龙」全部完成资本交卷 |
2. 10 平台横向对比矩阵
2.1. 基本信息与定位矩阵
| # | 平台 | 定位 | 最新产品 | 生态 | 适用边界 |
|---|---|---|---|---|---|
| 01 | NVIDIA | 全栈生态霸主 | GB200/GB300 NVL72;Vera Rubin NVL144 规划 | CUDA + TensorRT-LLM + NIM + Dynamo(封闭闭环) | 无国产化硬约束的性能首选 |
| 02 | AMD | 追赶者与开源 ROCm | MI355X;Helios 机柜(2026) | ROCm 7 开源 + vLLM/SGLang 适配 + UALink | 推理性价比敏感、多供应商策略 |
| 03 | 华为昇腾 | 国产全栈 + 超节点差异化 | CloudMatrix 384;950/960/970 路线图 | CANN + MindSpore + MindIE + vLLM-Ascend | 信创合规场景唯一完整解 |
| 04 | 寒武纪 | A 股 AI 芯片第一股 | 思元 590/690(营收主力) | Neuware + MagicMind(基础层) | 具备自研 infra 能力的头部客户 |
| 05 | 摩尔线程 | GPU 全功能路线 | MTT S5000;夸娥万卡集群 | MUSA 统一架构 | 省级智算中心、AI + 图形混合负载 |
| 06 | Google TPU | 云厂商自研自用 | Ironwood(第 7 代,推理优先) | XLA/JAX + Pathways + vLLM TPU 后端 | GCP 生态、稳定批量推理 |
| 07 | AWS Trainium | 云厂商规模化外供 | Trainium2 → Trainium3;Project Rainier | Neuron SDK + Bedrock 协同 | AWS 生态、超大规模单客户集群 |
| 08 | 海光/天数/燧原 | 国产二线三路线 | 深算系列 / 智铠 100 / S60 + L600 | DTK(类 CUDA)/ DeepSpark / TopsRider | 迁移型、自研型、推理型分别对应 |
| 09 | 开源推理 serving 生态 | L1/L4 标准件供应层 | vLLM V1、SGLang、TensorRT-LLM v1.0、MindIE 3.0.0 | PyTorch 基金会 + 多硬件插件制 | 自建推理服务的一切团队 |
| 10 | 训练框架生态 | L3 训练编排层 | Megatron-Core、torchtitan(4D 并行) | PyTorch 基金会 + NVIDIA/微软/AWS 支持 | 按模型规模走选型阶梯 |
2.2. Harness 六层成熟度矩阵
评级为基于公开资料的定性判断,非统一基准实测;「弱(不透明)」表示公开可查证机制缺失。
| # | 平台 | L1 上下文工程 | L2 工具执行 | L3 编排控制 | L4 记忆状态 | L5 评估观测 | L6 治理安全 | 整体形态 |
|---|---|---|---|---|---|---|---|---|
| 01 | NVIDIA | 强 | 强 | 中强 | 中强 | 强 | 中强 | 推理侧 Harness 地基供应商 |
| 02 | AMD | 中强 | 中强 | 中 | 中(弱层) | 中 | 弱~中 | 开源栈的硬件载体 |
| 03 | 华为昇腾 | 中强 | 中强 | 中强(大 EP 独有) | 中 | 中强 | 强(合规维度) | 国产全栈竖井 |
| 04 | 寒武纪 | 弱(不透明) | 中 | 弱(不透明) | 弱(不透明) | 弱~中 | 中 | 底层算力供应商 |
| 05 | 摩尔线程 | 中 | 中 | 中 | 中 | 中强(指标公开) | 强(合规维度) | 全功能 GPU 竖井 |
| 06 | Google TPU | 中强 | 中强 | 强(集群编排) | 中强 | 中强 | 强(云)/ 弱(私有化) | 云托管一体化 |
| 07 | AWS Trainium | 中强 | 中 | 中强 | 中 | 中强 | 强(云治理) | 垂直整合巨型集群 |
| 08 | 海光/天数/燧原 | 弱 | 中 | 弱~中 | 弱(不透明) | 弱~中 | 中强(合规维度) | 迁移/自研/推理三路线 |
| 09 | 推理 serving 生态 | 强 | 强 | 中强 | 强 | 中强 | 中强 | Harness 标准件层 |
| 10 | 训练框架生态 | 中强 | 强(NVIDIA 栈) | 强 | 强 | 中强 | 中 | 训练域编排层 |
矩阵的四个结构性读法:
- L1/L4 的强者是软件生态而非芯片厂商:PagedAttention/RadixAttention/KV 卸载等 L1/L4 核心创新全部出自开源推理生态(09 篇),硬件厂商的价值在于为这些创新提供物理容量(共享 HBM、全局内存池);
- L6 有两种「强」:海外云厂商的强是「云治理开箱即得」(GCP IAM、AWS 审计),国产厂商的强是「信创合规唯一解」——两者的客户群体几乎不重叠;
- L3 分化为三个物种:任务编排(智能体框架,02-AI-Agents 组范围)、推理请求编排(Dynamo/PD 分离)、训练拓扑编排(Megatron 并行策略)——同名不同物,引用时须区分;
- 寒武纪与整合篇的「弱」是公开度问题:客户自建上层生态导致其 Harness 能力不可见(弱·不透明),与真正的能力缺失必须区分。
2.3. 生态与适用边界速查
| 需求 | 首选 | 备选 | 关键理由 |
|---|---|---|---|
| 极致训练/推理性能与生态完备性 | NVIDIA NVL72 形态 | AMD MI355X(二供) | MLPerf 第三方可验证成绩唯一齐全 |
| 推理单位成本最优 | AMD(tokens-per-dollar 口径)/ Google TPU | 需实测 | 大显存 + 开放框架;TPU 需 GCP 生态 |
| 国产化合规(政务/金融/运营商) | 华为昇腾全栈 | 寒武纪、摩尔线程、海光 | 全栈竖井 + 案例密度最高 |
| 存量 CUDA 代码迁移 | 海光 DTK | 摩尔线程 MUSA | 类 CUDA 兼容路线 |
| GCP 生态稳定推理 | Google TPU(Ironwood) | — | 推理优先设计 + GKE 推理网关 |
| AWS 生态超大规模训练 | AWS Trainium(Rainier 形态) | — | 单客户巨型集群交付能力 |
| 自建推理服务(多硬件) | vLLM(多后端)+ Dynamo/llm-d | SGLang(Agent 密集) | 基金会中立 + 插件制 |
| 万卡级预训练 | Megatron-Core | DeepSpeed-MoE | 事实标准 + 经验 MFU 区间最高 |
3. 国产 vs 海外格局对比
3.1. 市场份额格局(IDC 2025 口径,B 级转述)
2025 年中国 AI 加速卡总交付约 400 万片,其中国产约 165 万片(41%):华为昇腾 81.2 万张(约 20.3%,国产第一)、寒武纪约 2.9%、燧原约 1.7%、沐曦与燧原相当;NVIDIA 约 220 万张(约 55%,主要来自管制前的存量与合规卡)。
3.2. 路线对比
| 维度 | 海外阵营 | 国产阵营 |
|---|---|---|
| 单卡性能 | 代际领先(Blackwell/Ironwood/Trainium3 年度节奏) | 单卡差距明显(910C 第三方口径约为 H100 的 60%) |
| 系统级弥补 | NVL72/超 Pod/UltraCluster | CloudMatrix 384(384 卡 + 光互联 + 内存池)、夸娥万卡 |
| 软件生态 | CUDA 锁定 vs ROCm/XLA/Neuron 分裂 | CANN 全栈 vs MUSA/DTK/Neuware/TopsRider 多头并进 |
| 验证体系 | MLPerf 第三方提交成熟(NVIDIA 完整、TPU/AWS 部分) | MLPerf 缺位,指标以公司口径为主 |
| 治理底盘 | 云治理(IAM/审计)+ 可持续发展口径 | 信创合规 + 全栈自主可控 |
| 客户结构 | 多元(云厂商、模型厂商、主权项目) | 集采与智算中心为主,头部客户集中度高 |
3.3. 三点综合判断
- 竞争单位已从芯片上移到系统:国产阵营以 CloudMatrix 384 / 夸娥万卡集群证明「以系统级规模补单卡差距」是可行路线,但代价是验证体系(MLPerf 级第三方基准)与软件生态(CUDA 护城河)仍需时间;
- 推理是国产阵营的窗口期:大 EP 推理、PD 分离、KV 管理等推理侧技术在 2025—2026 年才成为主战场,代际差距小于训练侧——昇腾大 EP(4 倍吞吐 / 15 ms 时延口径)、燧原推理放量(6.6 万张)均指向此;
- 多栈硬件中立成为头部模型厂商的标准策略:Anthropic 同时押注 NVIDIA GPU + Trainium(Rainier)+ TPU(百万颗承诺),NVIDIA 的份额优势正在被「二供 + 自研」结构性地稀释。
4. 关键口径冲突清单(并列呈现)
本组研究遵循「口径冲突并列、不择一」纪律,全部冲突集中列示如下,引用任何一方前必须阅读本节:
| # | 冲突 | 口径 A | 口径 B | 处理 |
|---|---|---|---|---|
| 1 | 华为超节点部署量 | 300 套(2025-09,昇腾产业峰会官方) | 750 套(2026-07,百度百科口径) | 时间基准不同,两者并列;中间无官方季度披露序列 |
| 2 | 昇腾 2025 出货量 | 63—64 万颗(第三方专家纪要,D 级) | 81.2 万张(IDC 报告转述,B 级) | 统计边界不同(芯片 vs 加速卡),并列并标注口径 |
| 3 | GB200 vs MI355X 推理性能 | GB200 约为 MI355X 的 28 倍(Signal65,NVIDIA 阵营引用) | MI355X FP4 吞吐高于 B200 1.3 倍(AMD 官方自测) | 均为厂商委托/自测,模型/精度/系统形态不可比 |
| 4 | TPU 成本优势 | 3 年 TCO 较 H100 集群低约 56%(第三方模型推算) | Midjourney 实践反思:省钱(约 65%)但拖慢研发迭代(C 级证言) | 稳定批量推理证据强,动态研究负载存在反例 |
| 5 | 厂商自测 vs 第三方 | NVIDIA:MLPerf A 级验证 | AMD/摩尔线程/华为关键指标均为厂商口径 | 本组已逐处标注「公司口径/厂商自报」 |
| 6 | 国产厂商客户订单 | 寒武纪客户订单、工商银行订单等均为媒体测算(D 级) | 公司官方从未披露客户名单与金额 | 正文只以「据公开报道(未经公司证实)」弱表述呈现 |
| 7 | Ironwood 单芯片 HBM 带宽 | 7.2 TB/s(Google 官方博客) | 7.37 TB/s(第三方汇编) | 以官方博客口径为准 |
5. 选型建议
5.1. 按约束条件选型
- 有国产化硬约束:按「全栈需求 → 华为昇腾;仅需裸算力 → 寒武纪;需要 GPU 通用性 → 摩尔线程;存量 CUDA 迁移 → 海光;推理集群 → 燧原」分流;
- 无国产化约束:按「性能优先 → NVIDIA;成本优先 → AMD/TPU 实测;云生态绑定 → 对应云厂商自研芯片」分流;
- 软件生态自主:无论硬件选择,推理侧默认以 vLLM/SGLang 为接口层(OpenAI 兼容 API),保留跨硬件迁移能力。
5.2. 采用前检查清单
- 口径核验:任何性能/利用率指标确认其来源级别(官方披露/公司口径/第三方基准/媒体测算),本组各篇信息缺口声明提供了对应核查入口;
- 基准实测:厂商口径指标(MFU、tokens/s、倍数)一律以自有负载实测替代后进入采购决策;
- 交付验收:算力采购遵循「机架上架才算数」原则(Anthropic CPO Mike Krieger 口径),把交付验收写入合同;
- 生态锁定评估:CUDA/ROCm/XLA/Neuron/CANN 的迁移成本测算应作为 TCO 的一部分;
- 验证体系缺口:国产平台选型时要求厂商提供 MLPerf 级第三方数据或接受联合实测,否则以最小规模 PoC 起步;
- 信息时效:本组全部数据以 2026-09-12 为截止,超节点/芯片代际迭代快(年度节奏),引用时注明检索日期。
6. 文档导航
| # | 文件 | 平台 | 一句话定位 |
|---|---|---|---|
| 01 | 01-nvidia.md | NVIDIA | GB200 NVL72 超节点与 CUDA 全栈生态(标杆篇) |
| 02 | 02-amd.md | AMD | MI355X 大显存 + ROCm 开源生态(追赶者篇) |
| 03 | 03-huawei-ascend.md | 华为昇腾 | CloudMatrix 384 超节点 + CANN 全栈 + 大 EP 落地(国产全栈篇) |
| 04 | 04-cambricon.md | 寒武纪 | 思元系列与云端商业化(A 股第一股篇) |
| 05 | 05-moore-threads.md | 摩尔线程 | MTT S5000 与夸娥万卡集群(GPU 全功能路线篇) |
| 06 | 06-google-tpu.md | Google TPU | Ironwood 与 Pods 互联拓扑(云厂商自研自用篇) |
| 07 | 07-aws-trainium.md | AWS Trainium | Project Rainier 与规模化外供(垂直整合篇) |
| 08 | 08-hygon.md | 海光/天数/燧原 | 国产二线三条技术路线整合篇 |
| 09 | 09-inference-serving.md | 推理 serving 生态 | vLLM/SGLang/TensorRT-LLM/MindIE(L1/L4 标准件篇) |
| 10 | 10-training-ecosystem.md | 训练框架生态 | Megatron-LM/DeepSpeed/FSDP/Colossal-AI(L3 训练编排篇) |
7. 研究局限与全局信息缺口
引用本组任何结论前,应先阅读以下全局性局限:
- 六层评级非统一基准实测:全部评级为基于公开资料的定性判断;算力平台无统一的智能体负载基准,横向可比数据稀疏且互不可比。
- 厂商自测 vs 第三方:除 NVIDIA(MLPerf A 级)外,AMD、摩尔线程、华为的关键性能/利用率数字均为厂商口径;本组已逐处标注,但读者不应将厂商口径视为已验证事实。
- 国产厂商订单与客户:寒武纪客户订单、工商银行订单等均为媒体测算/自媒体(D 级),公司无官方披露;正文仅以「据公开报道(未经公司证实)」呈现。
- 口径冲突逐项保留:见第 4 节清单,全部并列呈现、未强行归并。
- 官方原文待核:寒武纪 2025 年报、燧原招股书原文建议以巨潮资讯网/上交所披露原文二次核验;昇腾 910C 官方规格表、MindIE 3.0.0 新特性、Trainium3 完整规格等官方文档缺口已在各篇信息缺口声明逐条列示。
- MLPerf 最终锚点:本组引用的 MLPerf 数字来自 MLCommons 结果的厂商博客转述,正式引用建议以 mlcommons.org 结果库为最终锚点。
- 版本时效性:所有版本号、部署规模与功能可用性以 2026-09-12 检索时点为准;超节点与芯片代际按年度节奏迭代,临近变更包括:Vera Rubin NVL144(2026—2027)、Helios(2026)、Ascend 950/960/970(至 2028)、Trainium3(2025-12 发布)、Ironwood 全球化部署(2026 年中规划)。
- 地缘与政策变量:出口管制(H20 系列)、国产化采购政策、主权 AI 项目(Stargate、HUMAIN 等)均可能在短期内改变格局;本组仅记录 2026-09-12 前的可溯源事实,不作预测。
8. 参考资料
- NVIDIA Q2 FY2026 CFO Commentary — NVIDIA 投资者关系,2025。https://investor.nvidia.com/files/doc_financials/2026/Q226/Q2FY26-CFO-Commentary.pdf
- NVIDIA Blackwell Delivers Massive Performance Leaps in MLPerf Inference v5.0 — NVIDIA Technical Blog,2025。https://developer.nvidia.com/blog/nvidia-blackwell-delivers-massive-performance-leaps-in-mlperf-inference-v5-0/
- AMD Instinct MI350 Series GPUs: A Game Changer — AMD 官方博客,2025。https://www.amd.com/en/blogs/2025/amd-instinct-mi350-series-game-changer.html
- 昇腾 AI 产业峰会成功举行(300 套超节点、邮储银行实践)— 昇腾社区,2025-09。https://www.hiascend.com/activities/dynamic-news/555
- 寒武纪 2025 年年报要点 — 中国证券报·中证智能财讯,2026-03-13。<https://newzzbcx.cs.com.cn/cxnews.html?name=new20260313185352mwlpcfpa&random=dp7iRuOp>
- 摩尔线程 2025 年度暨 2026 年第一季度业绩说明会 — 中国证券网路演中心,2026。https://roadshow.cnstock.com/fbh/mexc2025
- Ironwood: 首款适用于 AI 推论时代的 Google TPU — Google 官方博客,2025-04。https://blog.google/intl/zh-tw/products/cloud/ironwood-the-first-google-tpu-for-the-age-of-inference/
- AWS 一周综述:Project Rainier 上线(2025-11-03)— AWS 官方中文博客,2025。https://aws.amazon.com/cn/blogs/china/aws-weekly-roundup-project-rainier-online-amazon-nova-amazon-bedrock-and-more-november-3-2025/
- 燧原科技科创板上市 开盘涨超 188% — 东方财富网(新华财经),2026-09-11。https://finance.eastmoney.com/a/202609113871802756.html
- PyTorch Foundation Welcomes vLLM as a Hosted Project — PyTorch 官方博客,2025。https://pytorch.org/blog/pytorch-foundation-welcomes-vllm/
- vLLM、SGLang 与 TensorRT-LLM 综合对比分析报告 — 阿里云开发者社区,2025。https://developer.aliyun.com/article/1686693
- 国产 AI 芯片崛起与场景化选型(IDC 2025 中国 AI 加速卡市场数据)— 腾讯云开发者社区,2026。https://cloud.tencent.cn/developer/article/2686867
- MLPerf Benchmarks 结果库 — MLCommons,2025。https://mlcommons.org/benchmarks/inference/
- 项目参数卡 v1.1(Harness 六层能力模型与 Harness Loop 统一口径)— 本项目内部基准文件。
- R16-AI-Infra 市场组检索报告 — 本项目内部检索报告(4 轮 24 次检索,约 90 条事实、66 条 URL)。
AI-Infra Group: Market Research on AI Compute Vendors' Landing Practices (Group Overview & Cross-Comparison)
1. Group Overview
1.1. Research Scope
This group (03-Market Research / 06-AI-Infra Group) conducts market research on the most representative 10 platforms/ecosystems in the 2026 AI compute industry, focusing on "specific vendor landing practices" — that is: who these compute platforms actually sold to, at what deployment scale, what results they delivered, and how well they can support upper-layer agent workloads.
Three categories of research subjects are covered:
- International leaders and chasers: NVIDIA (GB200 NVL72 + CUDA full stack), AMD (MI355X + ROCm), Google TPU (Ironwood), AWS Trainium/Inferentia (Project Rainier);
- Domestic leaders and second-tier: Huawei Ascend (CloudMatrix 384 + CANN full stack), Cambricon (Siyuan series), Moore Threads (MTT S5000 + Kuae cluster), Hygon Information / Tianshu Zhixin / Enflame Technology (integration chapter);
- Open-source software ecosystem: inference serving ecosystem (vLLM/SGLang/TensorRT-LLM/MindIE) and training framework ecosystem (Megatron-LM/DeepSpeed/FSDP/Colossal-AI).
Each platform has one dedicated document (see the Section 6 document navigation), uniformly following an eight-part structure: introduction, terminology, feature description & product line, platform architecture, Harness design (six-layer analysis), actual cases, summary, and references.
1.2. Division of Labor with the 02-Industry Enablement / 01-AI-Infra Group
This group has a clear division of labor boundary with the 02-Industry Enablement / 01-AI-Infra Group:
| Dimension | 02-Industry Enablement / 01-AI-Infra Group | This Group (03-Market Research / 06-AI-Infra Group) |
|---|---|---|
| Research subject | General technology stack: AI chips (GPU/NPU) → servers & supernodes → cluster interconnect & data centers → the technology system itself of training/inference frameworks & scheduling | Specific vendors: the productized landing and commercial practices of the above technology stack across vendors |
| Core question | "How does this type of technology work?" | "How well is this vendor doing, who do they sell to, and how credible are they?" |
| Content form | Directional documents (including AGENTS.md / SKILL.md specifications) | Market research documents (eight-part structure + six-layer rating + case matrix) |
| Cross handling | When both sides touch the same technical concept (e.g. supernodes, PD separation), technical principles go to the Industry Enablement group, while vendor claims and cases go to this group | Same as left |
1.3. Analysis Framework & Rating Basis
All platforms uniformly apply the Harness six-layer capability model defined by the project parameter card:
| Layer | Name | Responsibility |
|---|---|---|
| L1 | Context Engineering Layer | Determines what the model "sees": retrieval, compression, caching, prioritization (KV Cache reuse belongs to this layer) |
| L2 | Tool & Execution Layer | Determines what the model "can do": tool registration, sandbox, scheduling (inference engine's OpenAI-compatible API, Function Call belong to this layer) |
| L3 | Orchestration & Control Layer | Determines "in what order to act": planning, state machine, scheduling orchestration (parallel strategy orchestration, PD separation scheduling belong to this layer) |
| L4 | Memory & State Layer | Determines what to "remember": session state, checkpoints (KV persistence, training checkpoints belong to this layer) |
| L5 | Evaluation & Observability Layer | Determines "how well it performs": metrics, regression sets (MFU, TTFT/TPOT, cluster observability belong to this layer) |
| L6 | Governance & Security Layer | Determines what it "cannot do": permissions, audit, compliance (Xinchuang compliance, precision governance, enterprise support belong to this layer) |
Rating basis (four levels): Strong (native first-class citizen mechanism, configurable and extensible) / Medium-Strong (has a native mechanism but incomplete coverage) / Medium (requires users to compose it themselves, or only provides basic primitives) / Weak (largely missing, requires external systems to fill in). "Weak (opaque)" means publicly verifiable mechanisms are missing (not that actual product capability is missing).
Methodology statement that must be emphasized: All six-layer ratings in this group are qualitative judgments based on public materials, not measurements against a unified benchmark. There is no unified agent-workload benchmark across compute platforms; performance data is mostly vendor-sourced (repeatedly flagged by this group), and third-party verifiable data exists only for NVIDIA (complete MLPerf submissions), Google TPU (partial MLPerf submissions) and sporadic submissions by AWS/AMD. The ratings reflect "the density and depth of publicly verifiable mechanisms and evidence," not "production-environment measured performance."
1.4. Industry Landscape: Four Layers of Chip, Supernode, Cluster, and Framework
Figure 0-1 | AI Infra industry landscape and the position of this group's 10 platforms (four-layer view)
Note: drawn based on a synthesis of this group's 10 research documents; shipment share is per the IDC 2025 basis (as relayed via Tencent Cloud Community).
1.5. 2025–2026 Key Events Timeline
The following events directly shaped the competitive landscape of this group's 10 platforms, and each document expands on them accordingly:
| Time | Event | Impact |
|---|---|---|
| 2024-03 | NVIDIA GTC releases GB200 NVL72 | The supernode becomes the basic unit of competition |
| 2025-04 | Huawei Cloud Ecosystem Conference releases CloudMatrix 384, launched at scale in Wuhu | The domestic camp offers an answer to "bridging the single-card gap with system-level scale" |
| 2025-04 | Google Cloud Next 25 releases Ironwood (7th-gen TPU), proposing the "Age of Inference" narrative | Industry focus shifts from training to inference-side services |
| 2025-05 | vLLM and DeepSpeed join the PyTorch Foundation together | Neutral governance of open-source training/inference infrastructure takes shape |
| 2025-06 | AMD Advancing AI releases MI350 series and ROCm 7, previews Helios | The open-standards path formally counters the NVLink closed loop |
| 2025-06 | GB300 NVL72 (Blackwell Ultra) customer shipments begin | MLPerf Inference v5.1 debut refreshes all new benchmarks |
| 2025-09 | Ascend Industry Summit: cumulative 300 supernodes, Postal Savings Bank large-EP practice; HUAWEI CONNECT announces 950/960/970 roadmap | Huawei publicly discloses a three-year chip roadmap on an annual cadence for the first time |
| 2025-09 | TensorRT-LLM v1.0 (PyTorch-first + trtllm-serve) | The usability barrier for inference engines drops dramatically |
| 2025-11 | Project Rainier goes online (nearly 500,000 Trainium2) | A milestone in cloud vendors scaling in-house chips for external supply |
| 2025-11 | Ironwood GA announcement; Anthropic's million-TPU commitment advances | TPU moves from in-house use to primary supply for leading customers |
| 2025-12 | Moore Threads listed on the STAR Market ("first domestic GPU stock"); AWS re:Invent releases Trainium3 | Domestic GPU capitalization and international generational progress in parallel |
| 2026-03 | Cambricon 2025 annual report: first annual profit, first dividend, "U" mark removed | Business model validation of domestic AI chips completed |
| 2026-09-11 | Enflame Technology listed on the STAR Market (688801) | All "Four Little Dragons of Domestic GPU" complete their capital-market delivery |
2. Cross-Comparison Matrix of the 10 Platforms
2.1. Basic Information & Positioning Matrix
| # | Platform | Positioning | Latest Product | Ecosystem | Applicability Boundary |
|---|---|---|---|---|---|
| 01 | NVIDIA | Full-stack ecosystem hegemon | GB200/GB300 NVL72; Vera Rubin NVL144 planned | CUDA + TensorRT-LLM + NIM + Dynamo (closed loop) | Performance first choice when no domestic-substitution hard constraint |
| 02 | AMD | Chaser and open-source ROCm | MI355X; Helios rack (2026) | ROCm 7 open source + vLLM/SGLang adaptation + UALink | Inference price/performance sensitive, multi-vendor strategy |
| 03 | Huawei Ascend | Domestic full stack + supernode differentiation | CloudMatrix 384; 950/960/970 roadmap | CANN + MindSpore + MindIE + vLLM-Ascend | The only complete solution for Xinchuang compliance scenarios |
| 04 | Cambricon | The first A-share AI chip stock | Siyuan 590/690 (revenue mainstay) | Neuware + MagicMind (base layer) | Leading customers with in-house infra capabilities |
| 05 | Moore Threads | Full-capability GPU path | MTT S5000; Kuae 10k-card cluster | MUSA unified architecture | Provincial AI compute centers, AI + graphics hybrid workloads |
| 06 | Google TPU | Cloud vendor in-house design and use | Ironwood (7th gen, inference-first) | XLA/JAX + Pathways + vLLM TPU backend | GCP ecosystem, stable batch inference |
| 07 | AWS Trainium | Cloud vendor scaled external supply | Trainium2 → Trainium3; Project Rainier | Neuron SDK + Bedrock synergy | AWS ecosystem, ultra-large single-customer clusters |
| 08 | Hygon/Tianshu/Enflame | Domestic second-tier, three paths | ShenSuan series / Zhikai 100 / S60 + L600 | DTK (CUDA-like) / DeepSpark / TopsRider | Migration, in-house, and inference types respectively |
| 09 | Open-source inference serving ecosystem | L1/L4 standard-component supply layer | vLLM V1, SGLang, TensorRT-LLM v1.0, MindIE 3.0.0 | PyTorch Foundation + multi-hardware plugin system | All teams building their own inference serving |
| 10 | Training framework ecosystem | L3 training orchestration layer | Megatron-Core, torchtitan (4D parallelism) | PyTorch Foundation + NVIDIA/Microsoft/AWS support | Selection ladder by model scale |
2.2. Harness Six-Layer Maturity Matrix
Ratings are qualitative judgments based on public materials, not measurements against a unified benchmark; "Weak (opaque)" means publicly verifiable mechanisms are missing.
| # | Platform | L1 Context Engineering | L2 Tool Execution | L3 Orchestration Control | L4 Memory State | L5 Evaluation Observability | L6 Governance Security | Overall Profile |
|---|---|---|---|---|---|---|---|---|
| 01 | NVIDIA | Strong | Strong | Medium-Strong | Medium-Strong | Strong | Medium-Strong | Inference-side Harness foundation supplier |
| 02 | AMD | Medium-Strong | Medium-Strong | Medium | Medium (weak layer) | Medium | Weak~Medium | Hardware carrier of the open-source stack |
| 03 | Huawei Ascend | Medium-Strong | Medium-Strong | Medium-Strong (unique in large EP) | Medium | Medium-Strong | Strong (compliance dimension) | Domestic full-stack silo |
| 04 | Cambricon | Weak (opaque) | Medium | Weak (opaque) | Weak (opaque) | Weak~Medium | Medium | Bottom-layer compute supplier |
| 05 | Moore Threads | Medium | Medium | Medium | Medium | Medium-Strong (metrics public) | Strong (compliance dimension) | Full-capability GPU silo |
| 06 | Google TPU | Medium-Strong | Medium-Strong | Strong (cluster orchestration) | Medium-Strong | Medium-Strong | Strong (cloud) / Weak (private) | Cloud-hosted integrated platform |
| 07 | AWS Trainium | Medium-Strong | Medium | Medium-Strong | Medium | Medium-Strong | Strong (cloud governance) | Vertically integrated giant cluster |
| 08 | Hygon/Tianshu/Enflame | Weak | Medium | Weak~Medium | Weak (opaque) | Weak~Medium | Medium-Strong (compliance dimension) | Three paths: migration/in-house/inference |
| 09 | Inference serving ecosystem | Strong | Strong | Medium-Strong | Strong | Medium-Strong | Medium-Strong | Harness standard-component layer |
| 10 | Training framework ecosystem | Medium-Strong | Strong (NVIDIA stack) | Strong | Strong | Medium-Strong | Medium | Training-domain orchestration layer |
Four structural readings of the matrix:
- The strong players in L1/L4 are software ecosystems, not chip vendors: All the core L1/L4 innovations such as PagedAttention/RadixAttention/KV offloading come from the open-source inference ecosystem (chapter 09); the value of hardware vendors lies in providing physical capacity for these innovations (shared HBM, global memory pools);
- L6 has two kinds of "Strong": The strength of overseas cloud vendors is "cloud governance out of the box" (GCP IAM, AWS audit), while the strength of domestic vendors is "the only Xinchuang compliance solution" — the customer bases of the two barely overlap;
- L3 has branched into three species: task orchestration (agent frameworks, within the scope of the 02-AI-Agents group), inference-request orchestration (Dynamo/PD separation), and training-topology orchestration (Megatron parallel strategies) — same name, different things, and they must be distinguished when cited;
- Cambricon and the integration chapter's "Weak" is a transparency issue: customers building their own upper-layer ecosystems make its Harness capabilities invisible (weak-opaque), which must be distinguished from a real capability gap.
2.3. Ecosystem & Applicability Boundary Quick Reference
| Need | First Choice | Alternative | Key Reason |
|---|---|---|---|
| Extreme training/inference performance and ecosystem completeness | NVIDIA NVL72 form factor | AMD MI355X (second source) | Only provider with complete third-party verifiable MLPerf results |
| Optimal inference unit cost | AMD (tokens-per-dollar basis) / Google TPU | Needs measurement | Large memory + open frameworks; TPU requires the GCP ecosystem |
| Domestic-substitution compliance (government/finance/telecom) | Huawei Ascend full stack | Cambricon, Moore Threads, Hygon | Full-stack silo + highest case density |
| Migrating existing CUDA code | Hygon DTK | Moore Threads MUSA | CUDA-like compatibility path |
| Stable inference in the GCP ecosystem | Google TPU (Ironwood) | — | Inference-first design + GKE inference gateway |
| Ultra-large-scale training in the AWS ecosystem | AWS Trainium (Rainier form factor) | — | Single-customer giant-cluster delivery capability |
| Building own inference serving (multi-hardware) | vLLM (multi-backend) + Dynamo/llm-d | SGLang (agent-dense) | Foundation-neutral + plugin system |
| 10k-card-scale pretraining | Megatron-Core | DeepSpeed-MoE | De facto standard + highest empirical MFU range |
3. Domestic vs. Overseas Landscape Comparison
3.1. Market Share Landscape (IDC 2025 basis, B-grade relay)
China's total AI accelerator card deliveries in 2025 were about 4 million units, of which domestic brands accounted for about 1.65 million (41%): Huawei Ascend 812,000 units (about 20.3%, domestic No. 1), Cambricon about 2.9%, Enflame about 1.7%, with MXM roughly on par with Enflame; NVIDIA about 2.2 million units (about 55%, mainly pre-embargo inventory and compliant cards).
3.2. Route Comparison
| Dimension | Overseas Camp | Domestic Camp |
|---|---|---|
| Single-card performance | Generational lead (Blackwell/Ironwood/Trainium3 annual cadence) | Obvious single-card gap (910C third-party basis is about 60% of H100) |
| System-level compensation | NVL72 / Super Pod / UltraCluster | CloudMatrix 384 (384 cards + optical interconnect + memory pool), Kuae 10k-card cluster |
| Software ecosystem | CUDA lock-in, vs ROCm/XLA/Neuron fragmentation | CANN full stack, vs MUSA/DTK/Neuware/TopsRider multi-track advance |
| Validation system | Mature MLPerf third-party submissions (NVIDIA complete, TPU/AWS partial) | MLPerf absent; metrics mainly vendor-sourced |
| Governance foundation | Cloud governance (IAM/audit) + sustainability basis | Xinchuang compliance + full-stack self-controllable |
| Customer structure | Diverse (cloud vendors, model vendors, sovereign projects) | Mainly centralized procurement and AI compute centers, high leading-customer concentration |
3.3. Three Overall Conclusions
- The unit of competition has moved up from chips to systems: The domestic camp has proven with CloudMatrix 384 / the Kuae 10k-card cluster that "bridging the single-card gap with system-level scale" is a viable path, but at the cost of a validation system (MLPerf-level third-party benchmarks) and software ecosystem (the CUDA moat) that still need time;
- Inference is the domestic camp's window of opportunity: Inference-side technologies such as large-EP inference, PD separation, and KV management only became the main battlefield in 2025–2026, with a smaller generational gap than the training side — Ascend large EP (4× throughput / 15 ms latency, vendor basis) and Enflame inference ramping (66,000 units) both point to this;
- Multi-stack hardware neutrality has become the standard strategy for leading model vendors: Anthropic is simultaneously betting on NVIDIA GPU + Trainium (Rainier) + TPU (million-unit commitment), and NVIDIA's share advantage is being structurally diluted by "second sourcing + in-house design."
4. Key Claim-Conflict List (Presented Side by Side)
This group follows the discipline of "present conflicts side by side, do not pick one"; all conflicts are listed together below, and this section must be read before citing either party:
| # | Conflict | Claim A | Claim B | Handling |
|---|---|---|---|---|
| 1 | Huawei supernode deployment count | 300 units (2025-09, Ascend Industry Summit official) | 750 units (2026-07, Baidu Baike basis) | Different time bases; both presented side by side; no official quarterly disclosure series in between |
| 2 | Ascend 2025 shipment volume | 630–640k chips (third-party expert minutes, D-grade) | 812k units (IDC report relay, B-grade) | Different statistical boundaries (chips vs accelerator cards), presented side by side with basis noted |
| 3 | GB200 vs MI355X inference performance | GB200 about 28× of MI355X (Signal65, cited by the NVIDIA camp) | MI355X FP4 throughput 1.3× higher than B200 (AMD official self-test) | Both vendor-commissioned/self-tested; models/precision/system form not comparable |
| 4 | TPU cost advantage | 3-year TCO about 56% lower than an H100 cluster (third-party model projection) | Midjourney practice reflection: saves money (about 65%) but slows R&D iteration (C-grade testimony) | Strong evidence for stable batch inference; there are counterexamples in dynamic research workloads |
| 5 | Vendor self-test vs third party | NVIDIA: MLPerf A-grade validation | Key metrics of AMD/Moore Threads/Huawei are all vendor-sourced | This group has flagged "company basis / vendor self-report" in each place |
| 6 | Domestic vendors' customer orders | Cambricon customer orders, ICBC orders, etc. are all media estimates (D-grade) | Companies have never officially disclosed customer lists or amounts | Presented in the body only with the weak phrasing "according to public reports (not company-confirmed)" |
| 7 | Ironwood single-chip HBM bandwidth | 7.2 TB/s (Google official blog) | 7.37 TB/s (third-party compilation) | The official blog basis prevails |
5. Selection Recommendations
5.1. Selecting by Constraint Conditions
- With a hard domestic-substitution constraint: Route by "full-stack need → Huawei Ascend; bare compute only → Cambricon; GPU generality needed → Moore Threads; existing CUDA migration → Hygon; inference cluster → Enflame";
- Without a domestic-substitution constraint: Route by "performance first → NVIDIA; cost first → AMD/TPU measured; cloud-ecosystem lock-in → the corresponding cloud vendor's in-house chip";
- Software-ecosystem autonomy: Regardless of hardware choice, default to vLLM/SGLang as the interface layer (OpenAI-compatible API) on the inference side, retaining cross-hardware migration capability.
5.2. Pre-Adoption Checklist
- Claim verification: Confirm the source grade of any performance/utilization metric (official disclosure / company basis / third-party benchmark / media estimate); this group's information-gap statements in each chapter provide the corresponding verification entry points;
- Benchmark measurement: Always replace vendor-sourced metrics (MFU, tokens/s, multiples) with measurements on your own workload before they enter a procurement decision;
- Delivery acceptance: Compute procurement follows the "it only counts once it's on the rack" principle (per Anthropic CPO Mike Krieger), writing delivery acceptance into the contract;
- Ecosystem lock-in assessment: The migration cost of CUDA/ROCm/XLA/Neuron/CANN should be estimated as part of TCO;
- Validation-system gap: When selecting a domestic platform, require the vendor to provide MLPerf-level third-party data or accept joint measurement; otherwise start with a minimum-scale PoC;
- Information currency: All data in this group is current as of 2026-09-12; supernodes/chip generations iterate fast (annual cadence), so note the retrieval date when citing.
6. Document Navigation
| # | File | Platform | One-Line Positioning |
|---|---|---|---|
| 01 | [01-nvidia.md](01-nvidia.md) | NVIDIA | GB200 NVL72 supernode and CUDA full-stack ecosystem (benchmark chapter) |
| 02 | [02-amd.md](02-amd.md) | AMD | MI355X large memory + ROCm open-source ecosystem (chaser chapter) |
| 03 | [03-huawei-ascend.md](03-huawei-ascend.md) | Huawei Ascend | CloudMatrix 384 supernode + CANN full stack + large-EP landing (domestic full-stack chapter) |
| 04 | [04-cambricon.md](04-cambricon.md) | Cambricon | Siyuan series and cloud commercialization (first A-share stock chapter) |
| 05 | [05-moore-threads.md](05-moore-threads.md) | Moore Threads | MTT S5000 and the Kuae 10k-card cluster (full-capability GPU path chapter) |
| 06 | [06-google-tpu.md](06-google-tpu.md) | Google TPU | Ironwood and Pods interconnect topology (cloud vendor in-house design and use chapter) |
| 07 | [07-aws-trainium.md](07-aws-trainium.md) | AWS Trainium | Project Rainier and scaled external supply (vertical integration chapter) |
| 08 | [08-hygon.md](08-hygon.md) | Hygon/Tianshu/Enflame | Integration of three domestic second-tier technical routes |
| 09 | [09-inference-serving.md](09-inference-serving.md) | Inference serving ecosystem | vLLM/SGLang/TensorRT-LLM/MindIE (L1/L4 standard-component chapter) |
| 10 | [10-training-ecosystem.md](10-training-ecosystem.md) | Training framework ecosystem | Megatron-LM/DeepSpeed/FSDP/Colossal-AI (L3 training orchestration chapter) |
7. Research Limitations & Global Information Gaps
Before citing any conclusion from this group, the following global limitations should be read first:
- The six-layer ratings are not measurements against a unified benchmark: All ratings are qualitative judgments based on public materials; compute platforms have no unified agent-workload benchmark, and cross-comparable data is sparse and mutually incomparable.
- Vendor self-test vs third party: Except for NVIDIA (MLPerf A-grade), the key performance/utilization numbers of AMD, Moore Threads, and Huawei are all vendor-sourced; this group has flagged this in each place, but readers should not treat vendor claims as verified facts.
- Domestic vendors' orders and customers: Cambricon customer orders, ICBC orders, etc. are all media estimates/self-media (D-grade), with no official company disclosure; the body presents them only as "according to public reports (not company-confirmed)."
- Claim conflicts retained item by item: See the Section 4 list; all are presented side by side, not forcibly merged.
- Official original documents to be verified: The originals of Cambricon's 2025 annual report and Enflame's prospectus should be double-checked against the disclosures on CNINFO/SHSE; gaps in official documents such as the Ascend 910C official spec sheet, MindIE 3.0.0 new features, and Trainium3 full specifications have been listed item by item in each chapter's information-gap statement.
- MLPerf as the final anchor: The MLPerf figures cited by this group come from vendor-blog relays of MLCommons results; for formal citation it is recommended to use the mlcommons.org results library as the final anchor.
- Version currency: All version numbers, deployment scales, and feature availability are as of the 2026-09-12 retrieval point; supernodes and chip generations iterate on an annual cadence, with upcoming changes including: Vera Rubin NVL144 (2026–2027), Helios (2026), Ascend 950/960/970 (through 2028), Trainium3 (released 2025-12), and Ironwood global deployment (planned mid-2026).
- Geopolitical and policy variables: Export controls (H20 series), domestic-substitution procurement policy, and sovereign AI projects (Stargate, HUMAIN, etc.) may all change the landscape in the short term; this group only records traceable facts before 2026-09-12 and makes no predictions.
8. References
- NVIDIA Q2 FY2026 CFO Commentary — NVIDIA Investor Relations, 2025. https://investor.nvidia.com/files/doc_financials/2026/Q226/Q2FY26-CFO-Commentary.pdf
- NVIDIA Blackwell Delivers Massive Performance Leaps in MLPerf Inference v5.0 — NVIDIA Technical Blog, 2025. https://developer.nvidia.com/blog/nvidia-blackwell-delivers-massive-performance-leaps-in-mlperf-inference-v5-0/
- AMD Instinct MI350 Series GPUs: A Game Changer — AMD Official Blog, 2025. https://www.amd.com/en/blogs/2025/amd-instinct-mi350-series-game-changer.html
- Ascend AI Industry Summit Successfully Held (300 supernodes, Postal Savings Bank practice) — Ascend Community, 2025-09. https://www.hiascend.com/activities/dynamic-news/555
- Cambricon 2025 Annual Report Key Points — China Securities Journal / CS Smart Financial News, 2026-03-13. <https://newzzbcx.cs.com.cn/cxnews.html?name=new20260313185352mwlpcfpa&random=dp7iRuOp>
- Moore Threads 2025 Annual and 2026 Q1 Results Briefing — China Securities Network Roadshow Center, 2026. https://roadshow.cnstock.com/fbh/mexc2025
- Ironwood: The First Google TPU for the Age of Inference — Google Official Blog, 2025-04. https://blog.google/intl/zh-tw/products/cloud/ironwood-the-first-google-tpu-for-the-age-of-inference/
- AWS Week in Review: Project Rainier Goes Live (2025-11-03) — AWS Official Chinese Blog, 2025. https://aws.amazon.com/cn/blogs/china/aws-weekly-roundup-project-rainier-online-amazon-nova-amazon-bedrock-and-more-november-3-2025/
- Enflame Technology Listed on the STAR Market, Opening Up Over 188% — East Money (Xinhua Finance), 2026-09-11. https://finance.eastmoney.com/a/202609113871802756.html
- PyTorch Foundation Welcomes vLLM as a Hosted Project — PyTorch Official Blog, 2025. https://pytorch.org/blog/pytorch-foundation-welcomes-vllm/
- Comprehensive Comparative Analysis Report of vLLM, SGLang and TensorRT-LLM — Alibaba Cloud Developer Community, 2025. https://developer.aliyun.com/article/1686693
- The Rise of Domestic AI Chips and Scenario-Based Selection (IDC 2025 China AI Accelerator Card Market Data) — Tencent Cloud Developer Community, 2026. https://cloud.tencent.cn/developer/article/2686867
- MLPerf Benchmarks Results Library — MLCommons, 2025. https://mlcommons.org/benchmarks/inference/
- Project Parameter Card v1.1 (unified basis for the Harness Six-Layer Capability Model and the Harness Loop) — Internal baseline document of this project.
- R16-AI-Infra Market Group Retrieval Report — Internal retrieval report of this project (4 rounds, 24 searches, about 90 facts, 66 URLs).