创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

用两台DGX Station部署GLM-5.3

AI 总结

NVIDIA Technical Blog介绍如何使用vLLM,在两台互联的NVIDIA DGX Station上本地部署量化版GLM-5.3。该模型拥有7530亿参数,张量并行将权重与计算拆分到两台GB300,使约464GB的检查点完全驻留GPU内存,并通过单一OpenAI兼容API提供服务。NVIDIA的SPEED-Bench测试显示,并发为16时吞吐量达到607.8 token/s,并发升至32时降至385.0 token/s。

深度见解

该教程给出了超出单块GB300显存容量的大模型分布式部署方案和实测并发数据,但证据仅来自NVIDIA发布的单一来源。

Running a frontier-scale model locally means keeping all its weights in GPU memory; the largest models no longer fit on one machine. Two NVIDIA DGX Stations connected over ConnectX-8 RDMA serve one model through a single endpoint, with tensor parallelism splitting the model weights and computation across both GPUs. 

The NVIDIA GLM-5.3 NVFP4 model, a quantized version of Z.ai’s mixture-of-experts (MoE) model, has 753 billion parameters, with 40 billion activated per token. Sparse activation reduces computation, but all model weights still need to remain available because each token can be routed to different experts. At about 464 GB, the checkpoint exceeds the 252 GB of HBM3e on a single GB300 GPU. This tutorial uses two DGX Stations to keep the weights in GPU memory, with CPU weight offload disabled.

Before starting, connect the two Stations with the Connect Two DGX Stations playbook.

This post shows how to serve GLM-5.3 locally across two NVIDIA DGX Stations with vLLM, send a request, and measure behavior under concurrent load. Tensor parallelism (TP=2) splits the model’s tensors across the two GB300 GPUs. Both Stations compute every request, and Station A returns the answer through one OpenAI-compatible API. By the end, you’ll have a working endpoint and a baseline for how it behaves under load.

#GLM-5.3#NVIDIA#Z.ai#vLLM#NVIDIA DGX Station#NVIDIA GB300#SPEED-Bench

原文约 16 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。