Beam-1.0-501B-A23B
Serve Beam-1.0-501B-A23B with NVIDIA Dynamo on H200, B200, B300, GB200, or GB300.
Deploy Beam-1.0-501B-A23B with NVIDIA Dynamo on H200, B200, B300, GB200, or GB300. Choose your framework, GPU, and serving topology; the summary and commands update to match. SGLang and vLLM provide aggregated and disaggregated serving on all five GPU types, with KV-aware routing and NIXL prefill/decode transfer. All profiles enable DFlash2 with block length 8 and FP8 KV cache. H200 uses FP8 weights; B200, B300, GB200, and GB300 use NVFP4 weights.
Choose your deployment target
Prerequisites
- Install the Dynamo Kubernetes Platform
with the
nvidia.com/v1beta1CRD and the GPUs shown above. - The manifests use Dynamo 1.6.0 and NVIDIA’s Beam runtime images:
nvcr.io/nvidia/ai-dynamo/sglang-runtime:1.6.0-beam-1.0-501b-dev.1ornvcr.io/nvidia/ai-dynamo/vllm-runtime:1.6.0-beam-1.0-501b-dev.1. - Prepare the
shared-model-cachePVC and Hugging Face checkpoints using the model-staging instructions. Configure storage, registry access, and GPU placement for your cluster.
Stage the FP8 checkpoint for H200 or the NVFP4 checkpoint for B200, B300, GB200, and GB300, plus the DFlash2 drafter for every target.
Provide RDMA device access and a working NIXL/UCX path between the prefill and
decode workers. Set the device-plugin resources and UCX_NET_DEVICES for your
cluster, and allow the runtime’s transport ports between workers. SGLang uses
bootstrap port 8998; vLLM uses NIXL side-channel port 5600 at each worker’s
pod IP. Both roles must use the same checkpoint, KV-cache format, and DFlash2 settings.
Deploy
From the repository root, set the profile for your selected target:
Before deploying, follow the
model-staging instructions
for your selected PROFILE. Use the namespace containing that staged model cache.
Use your cluster overlay for GPU and CPU-architecture placement when nodes differ.
On a cluster with matching hardware, apply the portable manifest below:
Smoke Test
In another terminal, send a streaming request through the Dynamo frontend:
Configurations
SGLang and vLLM share these defaults and deployment layouts. Blackwell includes B200, B300, GB200, and GB300; P/D means prefill/decode.
The selected deploy.yaml contains the attention and MoE backends, batching,
cache, and memory settings. Measured performance results are not included.
Related Feature Benchmarks
Browse the Feature Benchmarks for KV-routing, disaggregation, and speculative-decoding studies.