当前位置:首页 > 报告详情

GPU Communication Library in Meta-Scale AI Clusters.pdf

上传人: S** 编号:1240953 2026-05-16 11页 763.13KB

1、GPU Communication Libraryin Meta-Scale AI ClustersJames Hongyi ZengMetaAI CLUSTERSMetas AI Clusters Getting Big 1GW,Announced 2026Lebanon,IndianaUp to 5GW,ETA 2028HyperionRichland Parish,Louisiana1GWPrometheusNew Albany,OhioDiverse Communication NeedsLLM StagesExample ChallengesCritical CommsExample

2、 OSS FrameworksExample OSS Comms LibrariesPre-TrainingMaximize massive throughput across thousands of GPUsFSDP(AllGather/ReduceScatter)torchtitan,Megatron-LMNCCL,RCCLPost-Training(RLHF)Rapid weight shipping from Learners to ActorsP2P(Send/Recv)torchforge,verlRay RPCInferenceKV Cache shipping for Pre

3、fill-Decode disaggregationP2P(Send/Recv)Expert Parallelism(AlltoAll)vLLM,SGLangDeepEP,Mooncake TEPre-training:Fault Tolerance Frequent failures are inherent risk for large scale synchronous pre-training18 min at 100K GPUs10 min restart time8 min effective training!Diverse set of interruptionUnavoida

4、ble Hardware FailuresPre-training:Fault Tolerance Solution:Parallelism Aware Fault ToleranceDivide GPUs into multiple replicasSame rank in each replica communicates with AllReduceDynamically scale up and downMeta Collective Communication Library(MCCL)Fast recoveryOne replica down,the rest continuesF

5、ast fault localizationSpare machines to restart replicaInference:Device Centric Communication High performance Mixed-of-Experts(MoE)is important for InferenceAll2All communicationDevice Centric CommunicationHost-based GPUDirect Async(aka IBRC)Device-native GPUDirect Async RDMA(aka IBGDA)Existing Lib

6、rariesNVSHMEMNCCL GPU Initiated Networking(GIN)Host-based GPUDirect Async(aka IBRC)Device-native GPUDirect Async RDMA(aka IBGDA)Inference:Device Centric Communication Pipes Work in progress,Open sourcing soon Device-native communication framework for writing c

word格式文档无特别注明外均可编辑修改,预览文件经过压缩,下载原文更清晰!
三个皮匠报告文库所有资源均是客户上传分享,仅供网友学习交流,未经上传用户书面授权,请勿作商用。
1. **Meta AI集群规模**:计划2026年建成1GW(印第安纳州利伯蒂),2028年达5GW(路易斯安那州里奇兰),2023年已有1GW(俄亥俄州新奥尔巴尼)。 2. **通信需求与挑战**: - **预训练**:需最大化千卡GPU吞吐(如FSDP的AllGather/ReduceScatter),故障恢复时间仅8分钟(原10分钟重启)。 - **推理**:MoE需All2All通信,采用设备中心通信(IBRC/IBGDA)及NVSHMEM/GIN。 3. **开源方案**: - 推出Torchcomms API,整合NCCLX/RCCLX、CTRAN(零拷贝传输)等技术,提升开发与部署效率。 - 开源MCCL(并行容错)与Pipes(设备原生通信框架),支持AMD/NVIDIA/BRCM多硬件。 4. **社区协作**:通过开源(github.com/meta-pytorch/torchcomms)推动标准化,联合社区优化GPU通信栈。
**AI集群通信挑战?** **GPU通信库如何优化?** **开源通信栈有何创新?**
客服
商务合作
小程序
服务号
折叠