AI Infra 组概述
1. 组定位:L2 执行层的物理底座
1.1. 全系列图景
AI Infra(人工智能基础设施)是承载大模型训练与推理的物理与软件底座。在 AI Harness 六层能力模型中,本组覆盖的是 L2 执行层的物理底座:芯片与超节点决定智能体"能做什么"的物理上限,训推框架是 L2/L3 的调度中枢,运维与可观测对应 L5/L6(评估观测与治理)。
本组采用全系列写法,按"芯片 → 超节点 → 集群互联与机房 → 训推框架 → 运维"五个环节组织。这条主线的权威背书来自华为全联接大会 2025 的判断:"超节点已经成为主导性产品形态,并正在成为 AI 基础设施建设的新常态""超节点事实上就是一台能学习、思考、推理的计算机,物理上由多台机器组成,但逻辑上一台机器"(A级,华为官方)。
截至 2025 年末,全国已建成万卡智算集群 42 个;全国智能算力规模(FP16)2025 年末为 1590 EFLOPS、2026 年 3 月末为 1882 EFLOPS(据工信部数据,B 级)。2025 年我国算力中心用电量 1960 亿千瓦时(同比 +18.1%),预计 2030 年突破 5000 亿千瓦时(中国信通院口径,B 级)。规模与能耗的同时膨胀,决定了本组各方向都必须在"算得快"与"算得起"之间做工程权衡。
图 0-1|AI Infra 全系列栈与 Harness 六层映射
示意图:基于本组文档分析绘制,六层定义引自 AI Harness 参数卡 v1.1。
1.2. 与 04-硬件研发组的关系:设计到运行的闭环
既有文档 AI Infra(设计侧) 已覆盖 AI Infra 的设计侧(GB200 NVL72 硬件规格全表、摩尔线程夸娥、国产万卡格局出货数据、AlphaChip/PrefixRL 等"AI 设计 AI 芯片"飞轮)。本组写运行侧全系列:芯片路标与运行参数、超节点运行形态、集群互联与机房运行数据、训练与推理框架、运维容错。
两组共同构成"设计 → 运行"闭环:设计侧的封装(CoWoS、HBM)决定运行侧的显存上限;运行侧的故障画像(Llama 3 的 419 次意外中断、GPU 相关占 58.7%)又反向驱动设计侧的可靠性目标。涉及设计侧细节时,本组文档统一以"详见 02-行业赋能/04-硬件研发组"交叉引用,不重复展开。
1.3. 四个方向的功能定位对比
| 方向 | 文档 | 核心问题 | 决定什么 | 关键指标 |
|---|---|---|---|---|
| AI 芯片 | 01-chip.md | 单芯片能算多快、装多少 | 物理上限(算力、显存、互联) | FP8/FP4 算力、HBM 容量与带宽、互联带宽 |
| 服务器与超节点 | 02-supernode.md | 如何把数百卡聚成"一台计算机" | L2 执行单元的边界 | 机架算力、内存池容量、系统时延 |
| 集群互联与机房 | 03-cluster.md | 如何连接、供电与散热 | 集群规模上限与运行成本 | 互联带宽、网络利用率、PUE |
| 训练框架与调度 | 04-training-framework.md | 万卡如何并行且持续运行 | 有效训练时间 | MFU、ETTR、有效训练时长占比 |
| 推理框架与 serving | 05-inference-framework.md | 如何低成本低延迟地出 token | 单位 token 成本 | TTFT、TPOT、每 token 成本 |
| 运维与可观测 | 06-ops.md | 故障如何被检测、隔离与恢复 | 集群可持续性 | 故障检测时延、隔离粒度、恢复耗时 |
1.4. 方向与 Harness 六层映射
下表为全组统一使用的映射基准(各方向文档引用时不得自行改写):
| 方向 | L1 上下文 | L2 执行 | L3 编排 | L4 记忆 | L5 评估 | L6 治理 |
|---|---|---|---|---|---|---|
| 01 芯片 | 显存容量/带宽决定上下文承载 | 芯片 = 执行底座物理基座 | — | — | 数据格式决定精度-性能权衡 | 出口管制/国产化约束 |
| 02 超节点 | 内存池化/统一编址支撑 KV 共享 | 超节点 = 单机化执行单元 | 域内调度简化 | 全局统一内存 | — | 液冷/供电合规 |
| 03 集群机房 | Scale-up 网络承载内存语义 | 集群网络 = 分布式执行总线 | 拓扑感知调度 | — | 网络利用率 | PUE/绿电/能耗预算 |
| 04 训练 | 数据管线 | — | 并行策略/checkpoint/弹性恢复 | 异步 checkpoint | MFU/ETTR/MLPerf | 配额与作业优先级 |
| 05 推理 | PagedAttention/RadixAttention/KV 池化 | serving 引擎 = 运行时 | PD 分离/continuous batching | KV Cache 持久化 | TTFT/TPOT/每 token 成本 | 多租户/计量 |
| 06 运维 | — | 硬件健康监控 | 容错调度/五步 SOP | 检查点/状态恢复 | 故障画像/SDC 治理 | 自动化分级 |
2. 共性挑战与对策
2.1. 规模:故障从异常变为常态
万卡以上规模下,硬件故障不再是异常事件。Meta Llama 3 405B 训练的 54 天快照显示:466 次作业中断中 419 次为意外中断,约每 3 小时一次;意外中断中 GPU 相关占 58.7%(A级,官方技术报告)。全组的对策是统一的容错思路——把故障从全局事件降级为局部事件:MegaScale 的"心跳检测 → 自检 → 隔离 → 补位 → checkpoint 恢复"五步流水线(arXiv 2402.15627,A级)、摩尔线程的 DP 组级隔离与零中断备机接入(B 级,厂商口径),以及 Llama 3 的异步 checkpoint + 热备节点组合。详见 04-training-framework.md 与 06-ops.md。
2.2. 能耗:PUE 政策红线与液冷
国家发改委等四部门《数据中心绿色低碳发展专项行动计划》(2024-07)明确:到 2025 年底新建及改扩建大型/超大型数据中心 PUE 不超过 1.25,国家枢纽节点项目不超过 1.2,国家枢纽新建数据中心绿电占比超过 80%(A级,政策原文)。这意味着供配电与散热不再是机房专业的"后置问题",而是芯片选型与超节点形态的前置约束——Atlas 950 SuperPoD 采用柜间全光互联、Vera Rubin NVL72 采用"无线缆、无水管、无风扇"中板设计,都部分源于散热与布线的压力。详见 03-cluster.md。
2.3. 互联:多路线并行的标准竞赛
Scale-up 互联正处于三线竞赛格局:NVIDIA NVLink(封闭 + NVLink Fusion 半开放)、UALink 联盟(开放,2026-04 发布 2.0 并新增 In-Network Compute)、OCP ESUN/SUE(以太网基,博通 Tomahawk 6 为芯片基础)。国内并行推进 EthLink(字节)、Eth-X(腾讯)、OISA(中国移动)与华为灵衢(UnifiedBus)2.0 开放规范(A级,HC2025)。本组文档统一立场:各路线按"已量产 / 已发布规范 / 规划中"三态标注,不使用"已规模商用"描述尚无原生硅的路线(如截至 2026-09 仍以 800GbE 桥接过渡的 UALink)。详见 03-cluster.md。
2.4. 国产化:制程受限下的系统级创新
华为在 HC2025 明确判断:"中国半导体制造工艺将长期落后、可持续算力只能基于实际可获得的制程"(A级)。在此约束下,国产路线的共性选择是以系统补单点:CloudMatrix 384 用 384 张昇腾 910C 以 UB 网络互联,以系统密集 BF16 约 300 PFLOPS 对标机架级竞品;昇腾按"一年一代"路标推进(950PR/950DT → 960 → 970),并自研 HiBL/HiZQ HBM 与 HiF8/HiF4 数据格式。本组统一要求:国产参数引用必须注明是否为论文实测(如 arXiv 2506.12708)或发布会口径,两者证据级别不同。
2.5. 度量:三个核心指标
与 04-硬件研发组 05-ai-infra.md 的结论一致并沿用:MFU(模型算力利用率)、ETTR(有效训练时间比率)、有效训练时长占比是本组所有效率结论的统一落点。推理侧增加 TTFT/TPOT/每 token 成本。任何"性能提升""效率提高"的模糊表述在组内文档与 AGENTS.md 中均被禁止;性能数字必须标口径(官方发布 / MLPerf / 第三方实测 / 厂商宣称)与硬件代际。
3. 文档导航
| 文件 | 内容 | 一句话定位 |
|---|---|---|
| AGENTS.md | 组级上位规范 | Infra 类任务的角色边界、集群操作红线与验收标准 |
| SKILL.md | 组级标准技能 | 集群效率诊断与容错编排的标准作业技能 |
| 01-chip.md | AI 芯片 | GPU/NPU 架构、显存、互联、国产化格局与路标 |
| 02-supernode.md | 服务器与超节点 | GB200 NVL72、CloudMatrix 384、Atlas 950/960、液冷 |
| 03-cluster.md | 集群互联与机房 | 三线互联竞赛、国内协议、供配电与 PUE 红线 |
| 04-training-framework.md | 训练框架与调度 | Megatron/DeepSpeed/FSDP、MegaScale、Llama 3、MLPerf |
| 05-inference-framework.md | 推理框架与 serving | vLLM/SGLang/TensorRT-LLM/MindIE、量化、PD 分离 |
| 06-ops.md | 运维与可观测 | checkpoint 容错、监控指标体系、故障域与 SDC 治理 |
建议阅读顺序:新成员按 01 → 02 → 03 → 04 → 05 → 06 自底向上;运维与 SRE 背景读者可从 06-ops.md 反向切入。
4. 总结
本组在 AI Harness 体系中的定位是 L2 执行层的物理底座:芯片与超节点决定"能做什么"的物理上限,训推框架是 L2/L3 的调度中枢,运维承担 L5 观测与 L6 治理。与 04-硬件研发组形成"设计 → 运行"闭环。全组三条主线贯穿始终:其一,故障常态化使容错编排(把故障从全局降级为局部)成为第一工程问题;其二,PUE 红线(1.25/1.2)与液冷转型使能耗成为与算力同级的前置约束;其三,互联标准多路线竞赛与国产化系统级创新,使"口径标注"(A级/B级/C 级、官方/实测/宣称)成为本组文档可信度的基础设施。
5. 参考资料
- 以开创的超节点互联技术,引领AI基础设施新范式(徐直军 HC2025 主题演讲)— 华为,2025-09-18。https://www.huawei.com/cn/news/2025/9/hc-xu-keynote-speech
- Serving Large Language Models on Huawei CloudMatrix384 — 华为/硅基流动,arXiv 2506.12708,2025-06。https://arxiv.org/pdf/2506.12708
- MegaScale: Scaling Large Language Model Training to More Than 10,000 GPUs — ByteDance,arXiv 2402.15627,2024。https://arxiv.org/abs/2402.15627
- The Llama 3 Herd of Models — Meta,2024。https://arxiv.org/abs/2407.21783
- MLPerf Training v5.0 结果发布 — MLCommons/PR Newswire,2025-06-04。https://prn.to/3Zlln3j
- NVIDIA Vera Rubin NVL72 产品页 — NVIDIA,2026-03。https://www.nvidia.com/en-us/data-center/vera-rubin-nvl72/
- 超节点关键技术与产业发展态势研究 — 中国热物理学会(转载),2025-2026。https://www.zgcsswdx.cn/info/24724.html
- 数据中心绿色低碳发展专项行动计划 — 国家发改委等四部门,2024-07。https://www.ndrc.gov.cn/
- 数据中心算力规模与能耗数据(政策解读转述,据工信部/中国信通院口径)— 中央网信办等七部门《促进数字化绿色化协同转型发展实施方案(2026—2030年)》解读,2026-09。
- AI Infra(设计侧,交叉引用)— 02-行业赋能/04-硬件研发组/05-ai-infra.md,2026-09-12。
AI Infra Group Overview
1. Group Positioning: The Physical Foundation of the L2 Execution Layer
1.1. Full-Series Landscape
AI Infra (artificial intelligence infrastructure) is the physical and software foundation that carries large-model training and inference. Within the AI Harness six-layer capability model, this group covers the physical foundation of the L2 execution layer: chips and supernodes determine the physical upper limit of what an agent "can do", training and inference frameworks are the scheduling hub of L2/L3, and operations and observability correspond to L5/L6 (evaluation, observation and governance).
This group is written in a full-series format, organized around five stages: "chip → supernode → cluster interconnect and data center → training-inference framework → operations". The authoritative endorsement for this main line comes from the judgment of Huawei Connect 2025: "Supernodes have become the dominant product form and are becoming the new normal for AI infrastructure construction", and "a supernode is in fact a computer that can learn, think and reason — physically composed of multiple machines, but logically a single machine" (A-level, official Huawei).
As of end-2025, 42 10,000-GPU-scale AI computing clusters had been built nationwide; the national intelligent computing capacity (FP16) stood at 1590 EFLOPS at end-2025 and 1882 EFLOPS at end-March 2026 (per MIIT data, B-level). In 2025, China's data-center electricity consumption was 1960 TWh (up +18.1% year-on-year), expected to exceed 5000 TWh by 2030 (CAICT methodology, B-level). The simultaneous expansion of scale and energy consumption determines that every direction in this group must make an engineering trade-off between "computing fast" and "computing affordably".
Figure 0-1 | AI Infra Full-Series Stack and Harness Six-Layer Mapping
Schematic: drawn based on the analysis of this group's documents; the six-layer definitions are quoted from the AI Harness parameter card v1.1.
1.2. Relationship with the 04-Hardware R&D Group: A Closed Loop from Design to Operation
The existing document AI Infra (Design) already covers the design side of AI Infra (the full GB200 NVL72 hardware specification table, Moore Threads Kua'e, domestic 10,000-GPU landscape shipment data, and the "AI designing AI chips" flywheel such as AlphaChip/PrefixRL). This group covers the full series on the operational side: chip roadmaps and operating parameters, supernode operational forms, cluster interconnect and data-center operational data, training and inference frameworks, and operations fault tolerance.
The two groups together form a "design → operation" closed loop: packaging on the design side (CoWoS, HBM) determines the memory ceiling on the operational side; the failure profile on the operational side (Llama 3's 419 unexpected interruptions, of which GPU-related ones account for 58.7%) in turn drives reliability targets on the design side. When design-side details are involved, this group's documents uniformly cross-reference "see 02-行业赋能/04-硬件研发组" rather than elaborating again.
1.3. Functional Positioning Comparison of the Four Directions
| Direction | Document | Core Question | What It Determines | Key Metrics |
|---|---|---|---|---|
| AI chips | 01-chip.md | How fast and how much a single chip can compute | Physical upper limit (compute, memory, interconnect) | FP8/FP4 compute, HBM capacity and bandwidth, interconnect bandwidth |
| Servers and supernodes | 02-supernode.md | How to pool hundreds of cards into "one computer" | Boundary of the L2 execution unit | Rack compute, memory pool capacity, system latency |
| Cluster interconnect and data center | 03-cluster.md | How to connect, power and cool | Cluster scale ceiling and operating cost | Interconnect bandwidth, network utilization, PUE |
| Training framework and scheduling | 04-training-framework.md | How tens of thousands of cards run in parallel and keep running | Effective training time | MFU, ETTR, proportion of effective training time |
| Inference framework and serving | 05-inference-framework.md | How to produce tokens at low cost and low latency | Cost per token | TTFT, TPOT, cost per token |
| Operations and observability | 06-ops.md | How faults are detected, isolated and recovered | Cluster sustainability | Fault detection latency, isolation granularity, recovery time |
1.4. Mapping of Directions to the Harness Six Layers
The table below is the unified mapping baseline used across this group (direction documents must not rewrite it on their own when citing):
| Direction | L1 Context | L2 Execution | L3 Orchestration | L4 Memory | L5 Evaluation | L6 Governance |
|---|---|---|---|---|---|---|
| 01 Chips | Memory capacity/bandwidth determines context carrying | Chip = physical base of the execution foundation | — | — | Data format determines precision-performance trade-off | Export controls/localization constraints |
| 02 Supernodes | Memory pooling/unified addressing supports KV sharing | Supernode = single-machine execution unit | Simplified intra-domain scheduling | Globally unified memory | — | Liquid cooling/power supply compliance |
| 03 Cluster/data center | Scale-up network carries memory semantics | Cluster network = distributed execution bus | Topology-aware scheduling | — | Network utilization | PUE/green power/energy budget |
| 04 Training | Data pipeline | — | Parallelism strategy/checkpoint/elastic recovery | Asynchronous checkpoint | MFU/ETTR/MLPerf | Quotas and job priority |
| 05 Inference | PagedAttention/RadixAttention/KV pooling | serving engine = runtime | PD separation/continuous batching | KV Cache persistence | TTFT/TPOT/cost per token | Multi-tenancy/metering |
| 06 Operations | — | Hardware health monitoring | Fault-tolerant scheduling/five-step SOP | Checkpoint/state recovery | Failure profile/SDC governance | Automation tiers |
2. Common Challenges and Countermeasures
2.1. Scale: Faults Change from Exception to Norm
At scales beyond 10,000 GPUs, hardware faults are no longer exceptional events. The 54-day snapshot of Meta Llama 3 405B training shows: of 466 job interruptions, 419 were unexpected — roughly once every 3 hours; GPU-related causes account for 58.7% of unexpected interruptions (A-level, official technical report). The group-wide countermeasure is a unified tolerance approach — degrading faults from global events to local events: MegaScale's five-step pipeline of "heartbeat detection → self-check → isolation → replacement → checkpoint recovery" (arXiv 2402.15627, A-level), Moore Threads' DP-group-level isolation and zero-interruption standby-machine insertion (B-level, vendor account), and Llama 3's combination of asynchronous checkpointing with hot-standby nodes. See 04-training-framework.md and 06-ops.md.
2.2. Energy: PUE Policy Red Line and Liquid Cooling
The "Special Action Plan for Green and Low-Carbon Development of Data Centers" (2024-07) from four national departments including the NDRC clearly states: by end-2025, the PUE of newly built and expanded/rebuilt large and super-large data centers must not exceed 1.25, national hub node projects must not exceed 1.2, and green power must account for over 80% of newly built national hub data centers (A-level, policy original text). This means power distribution and cooling are no longer "post-hoc problems" for the data-center discipline, but pre-constraints on chip selection and supernode form — Atlas 950 SuperPoD adopts cross-cabinet all-optical interconnect, and Vera Rubin NVL72 uses a "cable-less, water-pipe-less, fan-less" midplane design, both partly driven by the pressure of cooling and cabling. See 03-cluster.md.
2.3. Interconnect: A Standards Race with Multiple Parallel Paths
Scale-up interconnect is in a three-line competition: NVIDIA NVLink (closed + NVLink Fusion semi-open), the UALink consortium (open, released 2.0 in 2026-04 with added In-Network Compute), and OCP ESUN/SUE (Ethernet-based, with Broadcom Tomahawk 6 as the chip foundation). Domestically, EthLink (ByteDance), Eth-X (Tencent), OISA (China Mobile) and Huawei Lingqu (UnifiedBus) 2.0 open specification (A-level, HC2025) are advancing in parallel. This group's documents take a unified stance: each path is annotated with one of three states — "mass-produced / specification published / planned" — and the term "commercially scaled" is not used to describe paths lacking native silicon (such as UALink, which as of 2026-09 still transitions over 800GbE bridging). See 03-cluster.md.
2.4. Localization: System-Level Innovation under Process Constraints
Huawei made a clear judgment at HC2025: "China's semiconductor manufacturing process will lag behind for a long time, and sustainable compute can only be based on actually available process nodes" (A-level). Under this constraint, the common choice of the domestic route is to compensate for single points with systems: CloudMatrix 384 interconnects 384 Ascend 910C chips over a UB network, using system-dense BF16 of about 300 PFLOPS to benchmark against rack-level competitors; Ascend advances on a "one generation per year" roadmap (950PR/950DT → 960 → 970), and develops its own HiBL/HiZQ HBM and HiF8/HiF4 data formats. This group uniformly requires: domestic parameter citations must state whether they are paper measurements (e.g. arXiv 2506.12708) or launch-event statements, as the two carry different evidence levels.
2.5. Measurement: Three Core Metrics
Consistent with and inherited from the conclusion of 04-硬件研发组/05-ai-infra.md: MFU (model FLOPs utilization), ETTR (effective training time ratio) and the proportion of effective training time are the unified landing points for all efficiency conclusions in this group. On the inference side, TTFT/TPOT/cost per token are added. Any vague claim of "performance improvement" or "efficiency gain" is forbidden within this group's documents and AGENTS.md; performance figures must state their basis (official release / MLPerf / third-party measurement / vendor claim) and hardware generation.
3. Document Navigation
| File | Content | Positioning in One Sentence |
|---|---|---|
| AGENTS.md | Group-level superior specification | Role boundaries, cluster operation red lines and acceptance criteria for Infra-type tasks |
| SKILL.md | Group-level standard skills | Standard operating skills for cluster efficiency diagnosis and fault-tolerant orchestration |
| 01-chip.md | AI chips | GPU/NPU architecture, memory, interconnect, localization landscape and roadmap |
| 02-supernode.md | Servers and supernodes | GB200 NVL72, CloudMatrix 384, Atlas 950/960, liquid cooling |
| 03-cluster.md | Cluster interconnect and data center | Three-line interconnect race, domestic protocols, power distribution and PUE red line |
| 04-training-framework.md | Training framework and scheduling | Megatron/DeepSpeed/FSDP, MegaScale, Llama 3, MLPerf |
| 05-inference-framework.md | Inference framework and serving | vLLM/SGLang/TensorRT-LLM/MindIE, quantization, PD separation |
| 06-ops.md | Operations and observability | checkpoint fault tolerance, monitoring metric system, failure domains and SDC governance |
Suggested reading order: new members follow 01 → 02 → 03 → 04 → 05 → 06 bottom-up; readers with an operations/SRE background can enter in reverse starting from 06-ops.md.
4. Summary
This group's position in the AI Harness system is the physical foundation of the L2 execution layer: chips and supernodes determine the physical upper limit of what can be done, training and inference frameworks are the scheduling hub of L2/L3, and operations take on L5 observation and L6 governance. Together with the 04-硬件研发组, it forms a "design → operation" closed loop. Three main threads run through the whole group: first, the normalization of faults makes fault-tolerant orchestration (degrading faults from global to local) the primary engineering problem; second, the PUE red line (1.25/1.2) and the liquid-cooling transition make energy a pre-constraint on the same level as compute; third, the multi-path standards race in interconnect and system-level localization innovation make "basis annotation" (A/B/C levels, official/measured/claimed) the infrastructure of this group's document credibility.
5. References
- Leading a new paradigm for AI infrastructure with pioneering supernode interconnect technology (Keynote speech of Eric Xu at HC2025) — Huawei, 2025-09-18. https://www.huawei.com/cn/news/2025/9/hc-xu-keynote-speech
- Serving Large Language Models on Huawei CloudMatrix384 — Huawei/SiliconFlow, arXiv 2506.12708, 2025-06. https://arxiv.org/pdf/2506.12708
- MegaScale: Scaling Large Language Model Training to More Than 10,000 GPUs — ByteDance, arXiv 2402.15627, 2024. https://arxiv.org/abs/2402.15627
- The Llama 3 Herd of Models — Meta, 2024. https://arxiv.org/abs/2407.21783
- MLPerf Training v5.0 results release — MLCommons/PR Newswire, 2025-06-04. https://prn.to/3Zlln3j
- NVIDIA Vera Rubin NVL72 product page — NVIDIA, 2026-03. https://www.nvidia.com/en-us/data-center/vera-rubin-nvl72/
- Research on key technologies and industrial development trends of supernodes — Chinese Society of Thermophysics (repost), 2025-2026. https://www.zgcsswdx.cn/info/24724.html
- Special Action Plan for Green and Low-Carbon Development of Data Centers — four national departments including the NDRC, 2024-07. https://www.ndrc.gov.cn/
- Data-center compute scale and energy-consumption data (policy-interpretation recount, per MIIT/CAICT methodology) — interpretation of the <Implementation Plan for Promoting the Coordinated Green and Digital Transformation (2026—2030)> by seven departments including the Central Cyberspace Affairs Commission, 2026-09.
- AI Infra (design side, cross-reference) — 02-行业赋能/04-硬件研发组/05-ai-infra.md, 2026-09-12.