Skip to main content

Deployment

For all methods and hardware platforms, see the official SGLang installation guide. The two paths below match the Python / Docker toggle in the command panel.
Command
Then run the Python output of the command panel below in that environment.
Pick your hardware + recipe to generate the launch command. The three serving strategies cover the common operating points:
  • Low-Latency — fastest reply for a single user. Pick for chat.
  • Balanced — good speed with several users at once. Use for typical multi-user serving.
  • High-Throughput — most tokens per second across many users. Best for batch jobs.
The Flash Vision (Exp) variant runs on a dedicated preview Docker image, lmsysorg/sglang:dev-dsv4-flash-vision — its support (sgl-project/sglang#37253) has not shipped in a release yet. The command panel’s Docker mode emits that image automatically for Flash Vision cells; see the Flash Vision notes.
For a runnable end-to-end example, see the DeepSeek-V4-Flash demo notebook.

Panel controls (top of the command box):

  • Python / Docker — bare sglang serve … for an existing SGLang env, or a docker run … sglang serve … wrap against the per-hardware image from the Install SGLang panel above.
  • ⧉ Copy — copies the current command (with whichever framing is active) to your clipboard.
  • $ cURL — a sample request against localhost:30000 to confirm the server is up.
  • ⚙ Env — edits the placeholders (HOST_IP, PORT, HF_TOKEN, NODE_RANK, NODE0_IP) the command and cURL share. Persists in localStorage across cookbooks.
  • Verified / Not Verified badge — green when the (hw, variant, quant, strategy, nodes) combo has been run end-to-end on real hardware; yellow when auto-derived from a neighbor and not yet re-checked.

Playground

The Playground is where you experiment with SGLang features beyond the verified matrix. The Deploy panel above only emits combinations the SGLang team has signed off on; the Playground lets you turn on additional knobs on top of whichever cell the Deploy panel is currently showing. The base is read live from your Deploy selection — only your overrides change. The knobs come in two flavors:
  • Built-in SGLang features — parallelism overrides (TP / CP / DP-Attention — DP-Attention’s value is the DP degree, with off to disable), MoE backend + EP, reasoning / tool-call parsers, speculative-decoding presets, prefill/decode disaggregation, HiCache tiers, and HiSparse hierarchical sparse attention (decode-role only — the card appears once PD-Disagg mode is set to decode).
  • DeepSeek-V4 specific features — MegaMoE W4A8 / W4A4 fused kernel (Blackwell only; Hopper SM90 uses a separate all-FP8 MegaMoE path — see Configuration Tips below).
Lines highlighted green are added by your overrides; lines with red strikethrough were in the verified base but stripped by an override. When no override differs from the base cell, the playground inherits the base’s Verified badge; any actual change flips it to Not Verified until the new configuration is run end-to-end and submitted back.

Panel controls reuse Python / Docker · ⧉ Copy · $ cURL · ⚙ Env from the Deploy panel, plus one extra:

  • Submit ↗ — opens a pre-filled GitHub issue so you can land your override combo as a new verified cookbook cell. Shown only while the badge says Not Verified; click it once you’ve actually run the command on your hardware and confirmed it works.

1. Model Introduction

DeepSeek-V4 is the next-generation Mixture-of-Experts model from DeepSeek, released 2026-04-24 under an MIT License. The 0731 Flash and 0813 Pro refreshes add checkpoints with a bundled DSpark draft head, and the experimental Flash Vision checkpoint builds image understanding on top of the 0731 Flash base:
VariantTotal paramsActive (MoE)Use
DeepSeek-V4-Flash284B13Bsingle-node serving on B200 / B300 / GB200 / GB300 / H200 (TP=4); RTX PRO 6000 (TP=2); H100 (TP=8)
DeepSeek-V4-Flash-073130413BFlash Official (0731), with a bundled DSpark draft head; verified on 8×B200, 4×GB300, and 4×H200
DeepSeek-V4-Flash-Vision-Exp305B13BFlash Vision (Exp) — experimental multimodal (image-text-to-text): the 0731 Flash base + vision encoder & aligner; verified on 4×B200 (TP=4), requires the preview build
DeepSeek-V4-Pro1.6T49Bhigh-capacity: B200 / B300 (TP=8) · GB300 (TP=4) · H200 FP4 (TP=8) · GB200 (2-node, TP=8) · H200 FP8 (2-node, TP=16) · H100 (2-node, TP=16)
DeepSeek-V4-Pro-08131.65T49BPro Official (0813), with a bundled DSpark draft head; verified on 4×GB300 (TP=4) · B200 / B300 / H200 FP4 (TP=8) · GB200 (2-node, TP=8) · H100 (2-node, TP=16) · MI355X
The Instruct checkpoints ship as FP4 MoE experts + FP8 attention / dense (one mixed-precision checkpoint covers every FP4-capable GPU). Matching *-Base repos ship pure FP8 mixed and are for further pre-training only — not for chat or tool calling. Highlights: hybrid CSA + HCA attention (~27% inference FLOPs / ~10% KV cache vs DSv3.2 at 1M context), manifold-constrained hyper-connections (mHC), Muon optimizer, 1M-token context (32T+ pre-training tokens), three reasoning modes (Non-think / Think High / Think Max — use ≥ 384K context for Think Max), and a dedicated encoding_dsv4.encode_messages Python encoder + DSML tool-call grammar. Recommended generation: temperature=1.0, top_p=1.0. Resources: HuggingFace · Flash Official (0731) · Flash · Flash Vision (Exp) · Pro · Pro Official (0813) · ModelScope · Flash · Pro.

2. Configuration Tips

Concurrency & DeepEP dispatch buffer Must hold: max-running-requests × MTP_draft_tokens ≤ SGLANG_DEEPEP_NUM_MAX_DISPATCH_TOKENS_PER_RANK. Violating it blows DeepEP’s dispatch buffer at steady-state load (deep_ep.cpp:1105). When tuning, move --cuda-graph-max-bs-decode, --max-running-requests, and the env together. The generator currently picks values on the conservative side (mirroring an internal stress-test matrix). They run safely out of the box but likely leave throughput on the table — please tune them up toward your actual workload’s peak concurrency and report findings back so the defaults can be revised. Speculative decoding The original Flash and Pro recipes use EAGLE. Flash Official (0731) and Pro Official (0813) use the bundled DSpark draft head; see DSpark for its launch and tuning notes.
Do not use EAGLE on the checkpoints that bundle a DSpark head. On 0813, --speculative-algorithm EAGLE starts and serves without any error, but the draft head it binds accepts nothing — every decode batch logs accept len: 1.00, accept rate: 0.00, so you pay the draft cost for zero speedup. Output stays correct, which is what makes it easy to miss. Switch to --speculative-algorithm DSPARK; the startup log then reports Draft checkpoint bundles a DSpark head.
For the original Flash and Pro checkpoints:
  • low-latency: steps=3, draft-tokens=4 → largest win at bs=1.
  • balanced: steps=1, draft-tokens=2 → gentler MTP, reduces throughput hit at higher batch.
  • high-throughput: MTP disabled — at saturation the verify step costs more than it saves.
  • MTP runs on the v2 speculative path.
DGX Spark (2x GB10): Flash Official FP4 / NVFP4, Flash Vision FP4 The DGX Spark row has three recipes, all Balanced · Multi-Nodes: Flash Official (0731) · FP4, Flash Official (0731) · NVFP4, and Flash Vision (Exp) · FP4. None of these checkpoints fits one 128GB GB10, so every recipe runs TP=2 across two DGX Sparks connected over ConnectX-7 (RoCE). Every other DGX Spark combination is greyed out on purpose.
  • Docker image — all three cells use lmsysorg/sglang:dev-v4f-2dgx-v2, a preview build made only for DGX Spark (branch b12x-vision @ 452239a74f): it bakes in the SM12x b12x MoE (W4A8) and compressed-MLA attention kernels (#34878, #35899, #34018), the Flash Vision model support (#37253), the b12x image-prefill fix that lets Flash Vision serve images on SM12x, the NVFP4 MTP-layer dispatch fix, and the CuTeDSL and NCCL pins the GB10 pair needs. Do not use it on other hardware, and use the panel’s Docker mode — the bare Python command needs the b12x kernel package this image ships.
  • Run the same command on both Sparks with --node-rank 0 / --node-rank 1 and --dist-init-addr pointing at node 0 over the ConnectX-7 link. The docker run flags the panel emits (--network host --ulimit memlock=-1:-1 --cap-add IPC_LOCK --device /dev/infiniband) are what let NCCL use RDMA; without them NCCL silently falls back to TCP and decode slows by roughly 40%.
  • Env knobs in the cells are part of the recipe: SGLANG_SM120_FLASHMLA_BACKEND=b12x selects the b12x attention path, SGLANG_B12X_MAX_TOKENS must equal --chunked-prefill-size, and PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True avoids unified-memory fragmentation OOMs on GB10.
  • NVFP4 (nvidia/DeepSeek-V4-Flash-0731-NVFP4) — only the routed experts are NVFP4; attention, shared experts and the DSpark MTP layer stay in the checkpoint’s native formats. On SM12x that means three extra flags: --moe-runner-backend flashinfer_cutlass (b12x’s MoE is MXFP4-only and trtllm-gen kernels are sm100-only), --speculative-moe-runner-backend b12x (the DSpark draft’s MTP experts are MXFP4 and run on b12x), and --disable-shared-experts-fusion (HashTopK rejects fused shared experts under the cutlass runner). Throughput and DSpark acceptance match the FP4 cell within noise.
  • Flash Vision — images are served natively on the b12x recipe with the same flags as Flash Official (send image_url content on /v1/chat/completions, see Vision); text-only requests work unchanged. Expect roughly 15–20% lower text throughput than Flash Official on this checkpoint — its bundled DSpark head accepts fewer drafts (~3.2 vs ~3.9) — with text accuracy intact.
DeepSeek-V4-Flash-Vision-Exp (Experimental) deepseek-ai/DeepSeek-V4-Flash-Vision-Exp is DeepSeek’s first experimental multimodal V4 checkpoint: the 0731 Flash base plus a vision encoder and aligner, served through the same sglang serve flow with OpenAI-style image_url inputs (see Vision below). Select the Flash Vision variant in the Deploy panel for its recipes.
  • Preview build required — support lands via sgl-project/sglang#37253 and has not shipped in a release. Docker mode on the Flash Vision cells already emits the preview image lmsysorg/sglang:dev-dsv4-flash-vision; for a Python environment, install SGLang from that PR’s branch. The DGX Spark Flash Vision cell is the exception: it uses the DGX Spark image lmsysorg/sglang:dev-v4f-2dgx-v2 (see the DGX Spark notes).
  • Verified matrix — MMMU-Pro via sgl-eval at temperature 1.0, top-p 0.95, --reasoning-effort max.
  • Engine auto-configuration — the engine picks the flashinfer_mxfp4 MoE runner and auto-disables shared-experts fusion for this checkpoint (its HashTopK routing rejects fused shared experts); don’t pass --enforce-shared-experts-fusion.
  • Chunked prefill & radix cache stay enabled — the scheduler keeps image spans consistent automatically: chunked-prefill truncation points are span-aligned (an image span always prefills within a single extend, overshooting the chunk budget by at most one span), and a radix-cache prefix match ending deep inside an image span is re-issued from the span start.
  • Speculative decoding — the checkpoint bundles a DSpark head, and the low-latency recipes enable it with --speculative-algorithm DSPARK (verified with image batches on B200 via the MMMU-Pro round; the other hardware rows are pending verification). The balanced and high-throughput recipes run target-only: they use DP Attention, which DSpark is incompatible with on current releases. As on the 0731/0813 checkpoints, do not pass the EAGLE flags.
Shared experts fusion (Blackwell, flashinfer_mxfp4) On the Blackwell fp4 recipes (--moe-runner-backend flashinfer_mxfp4), the shared expert runs as a separate FP8 MLP on an alternate stream by default. Adding:
Command
routes it as one extra MXFP4 expert through the same trtllm-gen MoE kernel, so the whole MoE runs on a single stream (~4 fewer kernel launches and 2 fewer stream syncs per MoE layer). The shared expert is requantized from FP8 to MXFP4 at load time. Measured on GB200 tp4: gsm8k and AIME25 accuracy on par with the unfused baseline; Mean TTFT -13% to -21% and P99 ITL -15% to -53% at QPS 1-8 with neutral throughput. Only for deployments without expert parallelism (e.g. the single-node low-latency recipes): with moe_ep_size > 1 the flag is rejected at startup, unless the DeepEP/MegaMOE per-rank shared-slot path is in use. Not applicable to Flash Vision (Exp) — the engine auto-disables the fusion on that checkpoint. Compressed attention state dtype DeepSeek-V4 uses hybrid compressed attention for long-context efficiency. SGLANG_DSV4_COMPRESS_STATE_DTYPE controls the dtype of the C4 / C128 compressed attention state pools. Supported values are float32 / fp32 (default: float32) and bfloat16 / bf16. For BF16 on the offline compression path:
Command
This BF16 setting applies only to the compressed attention state pools and reduces the GPU memory footprint of each compressed-state slot. It does not change model weight precision or the main KV cache dtype. With automatic pool sizing and no explicit capacity cap, the same memory budget holds more slots, and the startup log shows larger c4_state and c128_state pool sizes. Keep the default float32 setting for the most conservative behavior. EPLB + Waterfill (Experimental) For recorded/static EPLB reproduction, first record an expert-distribution file by following Capture expert selection distribution in MoE models. For reproduction runs, use the generated expert_distribution_recorder_*.pt as the initial expert location. Please checkout to latest main branch for this feature. For non-PD reproduction, use:
Command
For PD-Disagg reproduction, use normal mode on the prefill server and low_latency mode on the decode server. Add the same --init-expert-location flag to both commands:
Command
You can also add --ep-num-redundant-experts and --eplb-algorithm to customize EPLB placement. Waterfill also supports MegaMOE. Use --moe-a2a-backend megamoe --enable-waterfill to keep the MegaMOE backend while applying Waterfill to the fused shared expert slot. FP4 Indexer (Experimental) DeepSeek-V4 uses the default indexer path unless --enable-deepseek-v4-fp4-indexer is set. Enable this flag to use the experimental FP4 C4 indexer. This path is intended for decode-heavy long-context workloads where reducing indexer cache bandwidth is beneficial. On NVIDIA (SM100 / SM120), pair the flag with DeepGEMM FP4 indexer support and the FlashInfer MXFP4 MoE runner:
Command
On AMD MI355X (gfx95), the AITER FP4 indexer kernels are available on ROCm. Keep the standard MI355 recipe and add only the indexer flag. Do not need to pass --moe-runner-backend flashinfer_mxfp4:
Command
NVFP4 Hybrid Checkpoints The nvidia/DeepSeek-V4-Pro-NVFP4 and nvidia/DeepSeek-V4-Flash-NVFP4 checkpoints quantize MoE experts to NVFP4 while keeping attention and dense layers in FP8. The official releases have matching NVFP4 checkpoints at nvidia/DeepSeek-V4-Flash-0731-NVFP4 and nvidia/DeepSeek-V4-Pro-0813-NVFP4. All of them require --moe-runner-backend flashinfer_trtllm_routed which will be automatically selected if not provided.
Command
or
Command
Requires Blackwell (SM100+). The MTP layer in this checkpoint stays MXFP4-packed and is routed through the Mxfp4FlashinferTrtllmMoEMethod path automatically. The official (0731 / 0813) NVFP4 checkpoints preserve the bundled DSpark draft head, so their low-latency recipes use --speculative-algorithm DSPARK instead of the EAGLE/MTP shape flags — same as the corresponding original-precision official checkpoints. Hopper (H100 / H200) note Two options are available for running DeepSeek-V4 on Hopper:
  • Original FP4 checkpoints — run the MoE experts with W4A16 kernels (Marlin or the FlashInfer SM90 CUTLASS runner) as the command generator picks for Hopper cells. With FlashInfer >= 0.6.18 you can instead select the W4A8 path — MXFP4 weights with FP8 activations via FlashInfer’s Humming kernels — by adding --flashinfer-mxfp4-moe-precision fp8 to --moe-runner-backend flashinfer_mxfp4; the low-latency Hopper cells now generate this form. Both work on H100 and H200; FP4 is the only option for H100 (no FP8 path). It is TP-only; on H200 the Pro variant fits on a single 8-GPU node, while H100 Pro needs 2 nodes (TP=16).
  • Converted FP8 checkpoints (H100 and H200 only) — pre-repackaged FP8 weights at sgl-project/DeepSeek-V4-Flash-FP8 and sgl-project/DeepSeek-V4-Pro-FP8 unlock DP-attention + DeepEP and richer parallelism (e.g. Pro TP=16 across 2 nodes).
On these FP8 checkpoints you can additionally enable the all-FP8 MegaMoE path on SM90 for higher long-context / large-decode throughput — see the SM90 (Hopper) FP8 MegaMoE note in Configuration Tips below. PD-Disagg recipes on H200 may require docker run --privileged --ulimit memlock=-1 (or --device /dev/infiniband:/dev/infiniband --cap-add IPC_LOCK) so mooncake can discover the IB HCAs; without IB exposure mooncake silently falls back to TCP, which can lead to garbled KV transfer on large checkpoints. RTX PRO 6000 (SM120 / Blackwell Desktop) note RTX PRO 6000 (96 GB) runs Flash only with the FlashInfer MXFP4 MoE runner. V4-Pro doesn’t fit on 8× 96 GB; the Deploy panel greys out unsupported recipes. HiCache and MegaMoE are not supported on RTX PRO 6000. AMD (MI300X / MI355X) note
  • Model checkpoints — for correct accuracy, the FP4 model uses the stock deepseek-ai/DeepSeek-V4-{Flash,Pro}, and the FP8 model uses the repackaged sgl-project/DeepSeek-V4-{Flash,Pro}-FP8.
  • Supported modelsMI300X supports DeepSeek-V4-Flash in FP8; MI355X supports DeepSeek-V4-Flash / Pro in both FP4 and FP8. All recipes run single-node.
  • TP / DP setting (MI355X) — both TP=4 and TP=8 are supported. At low concurrency we recommend TP-only; at high concurrency use TP + DP (balanced / high-throughput recipes). The verified MI355X DP recipes additionally set --dp 8 --enable-dp-attention --enable-dp-attention-local-control-broadcast --tokenizer-worker-num 8 --stream-interval 20 --prefill-decode-interval 10.
  • MTP — speculative decoding on the original Flash / Pro checkpoints; add --speculative-algorithm EAGLE --speculative-num-steps 3 --speculative-eagle-topk 1 --speculative-num-draft-tokens 4. The 0813 Pro Official checkpoint keeps its MTP head too, so the same flags are the speculative option under PD disaggregation — see the DSpark note below.
  • DSpark (MI355X Pro Official 0813) — the 0813 checkpoint bundles the DSpark draft head. Prefer it over EAGLE on 0813 for ordinary serving: enable --speculative-algorithm DSPARK (low-latency) and see the MI355X agentic recipe for the long-context path. The one exception is PD disaggregation, where DSpark cannot run at all and the Playground strips it — there, fall back to the MTP 3-1-4 shape above, as in §3.8.
  • Kernels — uses the Unified KV attention and the flydsl MoE.
  • FP4 indexer (MI355X) — FP4 C4 indexer is supported via --enable-deepseek-v4-fp4-indexer on top of the standard ROCm recipe.
  • Agentic long-context (MI355X Pro Official FP4) — TP-only serving adds --prefill-decode-interval 10 for scheduler stability. The DP path additionally needs --enable-dp-lm-head (required for DSpark under DP attention), --enable-prefill-delayer --prefill-delayer-token-usage-low-watermark 0.7 so a single long prefill does not monopolise the engine, plus the flags in the MI355X agentic recipe.
MoRI EP (AMD expert parallelism) On AMD, expert parallelism uses the MoRI all-to-all backend (--moe-a2a-backend mori), not DeepEP. Add the flags below on top of the verified recipe when sharding experts across GPUs; set --ep-size to the EP degree (typically the GPU count on one node). Two optional env vars improve MoRI throughput (both off by default):
Command
  • FP4: enable both env vars.
  • FP8: use SGLANG_MORI_RECV_BOUND=1 only; omit SGLANG_MORI_DISPATCH_DTYPE=mxfp8.
MegaMoE MegaMoE fuses expert dispatch + GEMM into a single kernel for higher throughput on MoE layers. To enable it, use the MegaMoE chip in the Playground below — the playground will swap --moe-a2a-backend deepep for --moe-a2a-backend megamoe and add the relevant launch settings automatically. Two variants are exposed:
  • W4A8 — default MegaMoE kernel (FP4 weights, FP8 activations).
  • W4A4 — adds --enable-w4a4-mxfp4-megamoe to run the custom W4A4 kernel (FP4 activations). The flag configures the required DeepGEMM settings. Higher throughput with negligible accuracy drop (~89.5 GPQA on Pro).
Notes:
  • The W4A8 / W4A4 variants above are Blackwell-only (B200 / B300 / GB200 / GB300). On Hopper (SM90, H100 / H200) use the all-FP8 MegaMoE path described below instead.
  • MegaMoE is only wired into the high-throughput recipe on Blackwell (per sgl-project/sglang#26451). The chip is hidden on low-latency and balanced — switch to high-throughput to expose it.
  • When running MegaMoE, don’t set --moe-runner-backend manually.
  • Adjust SGLANG_OPT_DEEPGEMM_MEGA_MOE_NUM_MAX_TOKENS_PER_RANK based on your workload and memory usage. Setting higher number of tokens for MegaMoE requires more HBM space (recommended: 8320 for high-throughput).
SM90 (Hopper) FP8 MegaMoE (Experimental) On SM90 (Hopper, H100 / H200), the all-FP8 MegaMoE path routes MoE through the DeepGEMM mega_moe runner for higher long-context / large-decode throughput on the FP8 checkpoints. Unlike the Blackwell W4A8 / W4A4 variants above, experts stay in FP8 — keep SGLANG_DSV4_FP4_EXPERTS=0. It requires a sgl-deep-gemm build with SM90 FP8 MegaMoE support. Please use the latest image for this feature. Enable the MegaMoE path with --moe-a2a-backend megamoe
Command
SGLANG_OPT_DEEPGEMM_MEGA_MOE_NUM_MAX_TOKENS_PER_RANK caps the number of tokens the MegaMoE path processes per rank (i.e. per GPU); the MegaMoE path is only used for batches at or below this cap. The right value depends on your parallelism / token-split scheme, and larger values reserve more HBM. GB300 PD-Disagg cross-pod MNNVL On some GB300 clusters with cross-pod KV transfer over NVLink, mooncake may fail with nvlink_transport.cpp:497 Requested address ... not found!. If this happens, prepend MC_FORCE_MNNVL=1 NCCL_MNNVL_ENABLE=1 NCCL_CUMEM_ENABLE=1 to both prefill and decode sglang serve commands.

3. Advanced Usage

3.1 Reasoning

Enable the deepseek-v4 reasoning parser (toggle Reasoning Parser in the Parsers card of the Playground above) to separate thinking from the final answer into reasoning_content vs content.
Example
Output

3.2 Tool Calling

Enable the deepseekv4 tool-call parser (toggle Tool Call Parser in the Parsers card of the Playground above) to surface structured tool calls via message.tool_calls.
Example
Output

3.3 HiCache (Hierarchical KV Caching)

HiCache enables multi-tier KV cache offloading (GPU → CPU → Storage), significantly expanding effective context capacity for long-context and multi-turn scenarios. Combined with UnifiedRadixTree, it provides intelligent prefix caching across all tiers. To enable HiCache, open the HiCache card in the Playground above and flip Enable:
  • L2 (GPU + CPU) — leave Storage on auto (default). Cold KV pages spill to CPU pinned memory only.
  • L3 (GPU + CPU + Storage) — pick a Storage backend (file / mooncake / hf3fs / nixl); the Playground emits the canonical page_first_direct mem-layout + direct IO backend + wait_complete prefetch policy, matching the HiCache best-practices recipe.
For AMD devices,
  • L2 (GPU + CPU) — leave Storage on auto (default). Cold KV pages spill to CPU pinned memory only. Use direct IO backend + page_first_direct or layer-first mem-layout.
  • L3 (GPU + CPU + Storage) — pick a Storage backend (file); the Playground emits the canonical page_first_direct mem-layout + direct IO backend + wait_complete prefetch policy, matching the HiCache best-practices recipe.
The Write policy knob defaults to write_through (the upstream default); switch to write_back / write_through_selective to trade durability for write speed when the storage tier is slow. For more details, see the HiCache documentation. For the alternative that skips the host tier entirely, see §3.9 UMBP — it is a sibling of HiCache, not a storage backend for it, and the two cannot be enabled together.

3.4 DSpark (Speculative Decoding)

Flash Official (0731) and Pro Official (0813) bundle a DSpark draft head in deepseek-ai/DeepSeek-V4-Flash-0731 and deepseek-ai/DeepSeek-V4-Pro-0813. The target and draft weights therefore come from the same checkpoint: enable DSpark with --speculative-algorithm DSPARK and do not set a separate --speculative-draft-model-path. The experimental Flash Vision checkpoint also bundles a DSpark head, enabled the same way: the Flash Vision low-latency recipes ship with --speculative-algorithm DSPARK (verified with image batches on B200 via the MMMU-Pro round; other hardware rows pending). The balanced and high-throughput Flash Vision recipes stay target-only because they run DP Attention. Unlike the EAGLE recipes for the original Flash and Pro checkpoints, this recipe omits --speculative-num-steps, --speculative-eagle-topk, and --speculative-num-draft-tokens. SGLang reads the DSpark shape from the checkpoint.
The Pro Official (0813) low-latency speed numbers in the Deploy panel were measured with SGLANG_SIMULATE_ACC_LEN=4, which pins the DSpark accept length at exactly 4.00. The recipe as shipped earns 4.678 on the same engine, so those rows read slightly conservative. The GSM8K figure for that cell is from the shipped command.
The verified 4×GB300 FP4 low-latency command is:
Command
Keep --mem-fraction-static 0.90 on this topology to leave enough headroom for the batch-256 verify graph. The first cold start can take 10–15 minutes while FlashInfer autotunes and SGLang captures the draft and verify graphs; later starts reuse the cache. This path is verified end-to-end on 4×GB300 with SGLang v0.5.16. Tune proposed draft tokens. --speculative-dspark-block-size N asks DSpark to propose N tokens per step; the target verifies a window of N + 1. If the flag is omitted, SGLang reads the value from the checkpoint. Both the 0731 and 0813 checkpoints resolve to five proposed tokens (the startup log reports gamma=5, verify_num_draft_tokens=6), which is the verified default. Use the DSpark Proposed Draft Tokens slider in the Playground to sweep one through five. Larger blocks can improve decode latency when acceptance stays high, but they also increase verification work and graph memory. Start from the checkpoint default, then sweep downward under the real prompt-length and concurrency distribution. The gain is usually largest for short interactive traffic and narrows as prefill dominates. Track P50/P99 TTFT and TPOT, total throughput, accepted length, GPU memory, and stop rate rather than choosing from acceptance alone. For every candidate, compare with the same recipe without --speculative-algorithm DSPARK. Restart the server between the DSpark and non-speculative legs, keep the request corpus, sampling, concurrency, and warmup identical, and give each bench_serving leg its own --flush-cache. Leave --speculative-draft-attention-backend unset unless a separate profiling run justifies an override. DSpark requires pp_size == 1. It is not compatible with PD disaggregation on current SGLang releases; selecting a prefill or decode role in the Playground automatically removes the inherited DSpark flags. The MI355X Flash Official recipes therefore run target-only, and so do the DP-Attention recipes in the Deploy panel — for DP-Attention configurations that do run DSpark, see the B200 agentic recipe and the MI355X agentic recipe. If a larger draft block or concurrency causes graph-capture OOM, lower --mem-fraction-static, the draft block size, or the configured maximum running requests, then rerun both performance and accuracy gates.

3.5 Vision (Image Inputs)

The experimental DeepSeek-V4-Flash-Vision-Exp checkpoint (the Flash Vision variant in the Deploy panel — see the configuration notes) takes images via the OpenAI-compatible image_url content type, as public URLs or base64 data: URIs; text and images mix freely in one message. Vision input works with the same server the Deploy panel produces — no extra model-specific flags needed.
Example
Output

3.6 Agentic Long-Context with HiCache DRAM Offload (B200 FP4, DSpark)

TP8, concurrency 8–16:
Command
DSv4 HiCache sizes the host tier with --hicache-ratio (host/device token ratio), not --hicache-size. Concurrency 1–5 runs the same command without the HiCache flags. DEP8 (DP Attention), concurrency 64–160:
Command
--chunked-prefill-size is a global budget divided by --dp, so this keeps 6144 tokens per rank.

3.7 Agentic Long-Context with HiCache DRAM Offload (MI355X FP4, DSpark)

DeepSeek-V4-Pro-0813 bundles the DSpark head, so --speculative-draft-model-path is not needed. --speculative-dspark-block-size 6 is the AL-optimal draft length on the committed golden curve (verify window 7). TP8, concurrency 1–16:
Command
Concurrency 32–48 keeps the same TP-only command and adds HiCache DRAM offload. DSv4 HiCache sizes the host tier with --hicache-ratio (host/device token ratio). Ratio 1.5 is the value that stays under a ~2.7 TB host DRAM budget at TP8:
Command
DP8 (DP Attention), concurrency 128–256:
Command
--chunked-prefill-size is a global budget divided by --dp, so this keeps 8192 tokens per rank. --enable-dp-lm-head is required for DSpark under DP attention.

3.8 PD Disaggregation on MI355X (MORI-IO)

On ROCm the prefill and decode roles talk over MORI-IO rather than Mooncake or NiXL, so the PD Disagg card in the Playground above hides the CUDA-only transports once MI300X / MI355X is selected and defaults the IB device list to the node’s rdmaN NICs instead of ConnectX mlx5_* names. Both roles need the RDMA NICs passed into the container, so the Docker output adds the fabric flags below on top of the usual ROCm device access from the Install panel. /dev/infiniband covers rdma_cm and the per-NIC uverbs0uverbs7 nodes, and the memlock/IPC_LOCK pair is what lets MORI-IO pin the buffers it registers with the NICs:
Command
--network host replaces the single-node -p mapping because the two roles rendezvous across hosts. Long agentic runs on the 1.6T checkpoint may need more than --shm-size 32g; raise it if the workers die during weight load. Selecting either role with MORI on MI355X emits the shared MORI-IO transport env — SGLANG_MORI_COMBINE_DTYPE plus the RDMA send-queue tuning MORI_IO_SQ_BACKOFF_TIMEOUT_US / MORI_IO_QP_MAX_SEND_WR — together with that role’s sizing. --max-running-requests is deliberately small on both: the pair streams KV between workers rather than holding a large running batch. The roles are sized per Strategy, so the Deploy panel’s operating point carries through to the PD command:
  • Low-Latency — TP-only, --mem-fraction-static 0.86, and a running-request ceiling of 8. Decode captures graphs for batches 1–8. No offload tier: the KV pool is all there is.
  • Balanced — still TP-only, with the ceiling at --max-running-requests 96 and a 16384 chunked-prefill budget. Decode ladders all the way to 96, since without DP the server-wide ceiling is the per-rank batch. Prefill runs a HiCache host tier (--hicache-ratio 2.5, page_first, write-through, best-effort prefetch); decode does not, because HiCache is not recommended on the decode role with MORI.
  • High-Throughput — inherits TP8 / DP8 and the 65536 chunked-prefill budget from the base cell, raises the ceiling to --max-running-requests 256 and --mem-fraction-static 0.92, and ladders decode to 32 — the per-rank batch 256 leaves across DP 8. It adds --enable-cache-report, which surfaces the prefix hit rate you need to judge whether an offload tier is paying for itself at that concurrency.
The offload tier is what actually separates balanced from high-throughput: balanced pairs prefill with HiCache’s tiered GPU → host cache, while high-throughput pairs it with UMBP, which links the radix tree straight to MORI with no host tier. They cannot both be on, and the Playground enforces that.
The low-latency and balanced roles are TP-only, and that is exactly why their decode ladders run to the full ceiling. Selecting either role forces DP-Attention off and grays the control: --max-running-requests is server-wide and floor-divided by attn_dp_size, so switching DP on would cut the per-rank batch below the captured graphs without changing either flag in the command. With PD off, the balanced cell stays a DP recipe for aggregated serving.
Speculative decoding (MTP) changes how you size the ceilings. For a target concurrency of N, set --max-running-requests N*2 on both roles. Sizing them at N caps the served batch below the concurrency you are aiming for. PD disaggregation requires EAGLE/MTP (DSpark cannot run under it), so this applies to every PD deployment.--max-running-requests is server-wide and floor-divided by attn_dp_size, so the decode graph ladder should cover the per-rank batch that leaves — N*2 / dp_size. That is why the two points above ladder to different places from ceilings that differ by less: balanced is TP-only, so 96 slots are 96 per rank, while high-throughput spreads 256 over DP 8 and only ever sees 32 at a time.
The high-throughput prefill role is where UMBP belongs — DP attention is already on, which is UMBP’s hard requirement, and the concurrency is high enough for the pool to matter. Turn on the UMBP card alongside the role; it is a separate card rather than part of the role because the linker flags are its to own, and leaving them implicit would hide the dependency. Whichever point you pick, the two roles diverge in two places:
  • Cuda graphs. Prefill runs eager (--disable-cuda-graph) because the FP4 indexer’s prefill path is not captured. Decode captures the small batch ladder that matches its running-request ceiling (--cuda-graph-bs-decode 1 2 3 4 5 6 7 8).
  • MORI dispatch budget. SGLANG_MORI_NUM_MAX_DISPATCH_TOKENS_PER_RANK is 16384 on prefill, sized for a whole chunked-prefill batch, and 128 on decode, where a step never dispatches more than a token per running request.
Note that DSpark is incompatible with PD disaggregation, so picking a role strips the inherited DSpark flags (see §3.4). For a speculative PD recipe use the bundled MTP head through the EAGLE path instead:
Command
Run the two roles on separate nodes with the same transport and IB device selection, then front them with the router the card prints. On MI355X that router is cache-aware rather than round-robin: --policy consistent_hashing keeps a conversation on the worker that already holds its prefix, which is what makes the agentic reuse pay off, and --balance-abs-threshold 2 / --balance-rel-threshold 1.1 keep that affinity from starving the peer given how small the running-request ceiling is. Health checks stay on with a long timeout so a wedged worker is still caught without a multi-minute prefill being mistaken for a failure. --dp-aware only does something when the workers run DP attention — turn on the Playground’s DP-Attention card if you want it to take effect, otherwise it is inert on the TP-only recipe above.

3.9 UMBP (Direct External KV Store)

UMBP is the second way to spill KV off the GPU, and it is an alternative to HiCache, not a tier inside it. HiCache is a hierarchy — GPU, then pinned host memory, then optionally a storage backend. UMBP links the unified radix tree straight to MORI’s buffer pool with no host cache tier in between, so pages load and offload against the external store directly. SGLang rejects the two together, so enabling the UMBP card in the Playground above strips the whole HiCache flag family from the command:
Command
The Store knob picks the linker backend. mori is the UMBP pool; mooncake drives the same direct-linker path against a Mooncake store instead. DP Attention is required, and the card’s Enable chip stays greyed out until you turn it on. This is not a soft preference. The linker keys its objects by rank, and MLA KV is replicated across TP, so a TP8 prefill worker under pure TP opens eight separate keyspaces holding eight copies of the same tokens — the pool’s effective distinct-token capacity would be an eighth of what its byte budget suggests, which is easy to mistake for a real measurement. DP attention collapses the keys onto one shared keyspace. Two further limits are worth knowing before you size a run. The pool is a per-node process, so a prefill worker that spans nodes would shard its keyspace by node. And only the prefill worker offloads KV — the decode side is untouched.