Muse-Spark-Open-816B-A42B
Serve Muse-Spark-Open-816B-A42B with Dynamo using SGLang or vLLM on GB200 and GB300.
This page covers serving Muse-Spark-Open-816B-A42B with SGLang (recommended) or experimental vLLM on GB200 and GB300.
Choose your deployment target
Video requests fail with the referenced Dynamo image because it does not include decord2, the package that provides SGLang’s decord video decoder. Frontend decoding (DYN_SGL_FRONTEND_DECODING=true) is not supported for image or video inputs in these disaggregated recipes. Select an aggregated SGLang recipe for video requests.
Prerequisites
- A Kubernetes cluster with the Dynamo platform installed and GB200 GPUs available. Use 4 GPUs (one node) for aggregated serving and 8 GPUs (two nodes) for either the disaggregated or KV-aware routed target.
- Access to the Muse-Spark-Open-816B-A42B checkpoint and tokenizer. The public model identifier is
meta-models/Muse-Spark-Open-816B-A42B-NVFP4. - Access to the SGLang runtime image referenced by the deployment manifest.
- ComputeDomain support with Dynamic Resource Allocation (DRA) enabled.
- A Kubernetes cluster with the Dynamo platform installed and GB300 GPUs available. Use 4 GPUs for aggregated serving and 8 GPUs for either the disaggregated or KV-aware routed target.
- Access to the Muse-Spark-Open-816B-A42B checkpoint and tokenizer. The public model identifier is
meta-models/Muse-Spark-Open-816B-A42B-NVFP4. - Access to the SGLang runtime image referenced by the deployment manifest.
- For disaggregated serving, ComputeDomain support with Dynamic Resource Allocation (DRA) enabled.
- A Kubernetes cluster with the Dynamo platform installed and 4 GB200 GPUs available.
- Access to the Muse-Spark-Open-816B-A42B checkpoint and tokenizer. The public model identifier is
meta-models/Muse-Spark-Open-816B-A42B-NVFP4. - Access to the vLLM runtime image referenced by the deployment manifest.
- A Kubernetes cluster with the Dynamo platform installed and 4 GB300 GPUs available.
- Access to the Muse-Spark-Open-816B-A42B checkpoint and tokenizer. The public model identifier is
meta-models/Muse-Spark-Open-816B-A42B-NVFP4. - Access to the vLLM runtime image referenced by the deployment manifest.
Deploy
1. Create the namespace and Hugging Face secret
2. Create shared storage
Edit recipes/muse-spark-open-816b-a42b/model-cache/model-cache.yaml and set storageClassName to a ReadWriteMany storage class available on the target cluster.
Then create the shared-model-cache PVC:
3. Download the model
The model-download manifest is preconfigured with the public model identifier. Apply it to populate the PVC and wait for the download to finish:
All worker manifests mount the shared-model-cache PVC at /model.
4. Deploy the selected target
This base omits provider-specific networking. Configure RDMA for long-context requests using a cluster Kustomization.
This base omits provider-specific networking. Configure RDMA for long-context requests using a cluster Kustomization.
The vLLM recipes use aggregated TP4/EP4 serving on 4 GPUs and mount the same shared-model-cache PVC.
Smoke Test
Wait for the selected deployment to become ready, then forward its frontend Service:
With either frontend forwarded, send a deterministic chat completion using the served model name meta-models/Muse-Spark-Open-816B-A42B-NVFP4:
Benchmark
Use perf.yaml to run AIPerf against the selected deployment. The agentic trace has approximately 64K input tokens, 400 output tokens, and 90% KV-cache reuse.
Select the workload
The selector provides the endpoint and workload settings for your recipe:
These settings replay the first 500 requests for functional validation, rather than the full trace.
Dataset
Place the benchmark trace at /model-cache/agentic.jsonl on the shared-model-cache PVC. The Job replays it with --custom-dataset-type mooncake_trace.
Run the benchmark
Restart workers between independent runs to reset KV-cache and routing state. After the previous Job completes, run from the repository root with the selected settings:
The Job runs five sequential warmup requests before replaying the trace.
Expected Performance
Disaggregated results were measured with cluster-specific RDMA networking.
The table lists the measured operating point for each of the six recipe targets.
These results cover the first 500 trace requests and establish functional operation. They are not full-trace performance runs and are not directly comparable to the SGLang results.
Compare All Targets
Source
- Deployment assets: Muse-Spark-Open-816B-A42B SGLang manifests
- Setup assets: model-cache.yaml and model-download.yaml
- Benchmark manifest: perf.yaml
- Deployment assets: Muse-Spark-Open-816B-A42B vLLM manifests
- Setup assets: model-cache.yaml and model-download.yaml
- Benchmark manifest: perf.yaml