Skip to main content

1. Model Introduction

The DeepSeek-V3.2 series includes three model variants, each optimized for different use cases: DeepSeek-V3.2-Exp is an upgraded version of DeepSeek-V3.1-Terminus, introducing the DeepSeek Sparse Attention (DSA) mechanism through continued training. DSA is a fine-grained sparse attention mechanism powered by a lightning indexer, enabling DeepSeek-V3.2-Exp to achieve significant efficiency improvements in long-context scenarios. Recommended for general conversations, long-context processing, and efficient inference. DeepSeek-V3.2 is the standard version suitable for general tasks and conversational scenarios. For local deployment, we recommend setting the sampling parameters to temperature = 1.0, top_p = 0.95. Recommended for standard conversations and general tasks. DeepSeek-V3.2-Speciale is a special variant designed exclusively for deep reasoning tasks. This model is specifically optimized for scenarios requiring complex logical reasoning and deep thinking. However this model does not support tool calls (see below). For local deployment, we recommend setting the sampling parameters to temperature = 1.0, top_p = 0.95. Recommended for deep reasoning tasks, complex logical problems, and mathematical reasoning. DeepSeek-V3.2-NVFP4 is an NVIDIA-optimized NVFP4-quantized variant of DeepSeek-V3.2 for Blackwell devices. It uses ModelOpt FP4 quantization with a choice of MoE runner backends (flashinfer_trtllm (recommended), flashinfer_cutlass, or flashinfer_cutedsl), enabling efficient deployment with lower tensor parallelism (TP=4). It supports the same features as DeepSeek-V3.2 including tool calling, reasoning, and speculative decoding (MTP). DeepSeek-V3.2-MXFP4 is an OCP-MXFP4 optimized variant for DeepSeek-V3.2 for AMD MI300X/MI355X devices. It uses OCP MXFP4 quantization with a triton mxfp4 backend (the same backend for gptoss-120B), enabling efficient deployment with lower tensor parallelism (TP=8) in a single node. It includes the same features as DeepSeek-V3.2 including tool calling, reasoning, fp8-kv, CP, TP and speculative decoding MTP.

2. SGLang Installation

SGLang offers multiple installation methods. You can choose the most suitable installation method based on your hardware platform and requirements. Please refer to the official SGLang installation guide for installation instructions.

2.1 Docker Images

Pre-built Docker images are available for different hardware platforms:
Command

3. Model Deployment

This section provides a progressive guide from quick deployment to performance optimization, suitable for users at different levels.

3.1 Basic Configuration

Interactive Command Generator: Use the configuration selector below to automatically generate the appropriate deployment command for your hardware platform, model variant, deployment strategy, and thinking capabilities. SGLang supports serving DeepSeek V3.2 on NVIDIA H200, B200, and AMD MI300X/MI355X GPUs.
All recipes here run the DSA indexer top-k on the default --dsa-topk-backend sgl-kernel. Other top-k backend choices have not been fully validated on DeepSeek-V3.2.

3.2 Configuration Tips

  • Short-sequence MHA prefill (adaptive): For prefill sequences shorter than 2048 tokens (default threshold), the DSA backend automatically switches to standard MHA (using FlashAttention variable-length on SM90, TRT-LLM ragged MHA on SM100). To extend this to longer sequences set env var SGLANG_DSA_PREFILL_DENSE_ATTN_KV_LEN_THRESHOLD to a larger value (potential minor accuracy trade-off).
  • DSA prefill/decode attention kernels (--dsa-prefill-backend, --dsa-decode-backend): The dsa backend is automatically selected for DeepSeek-V3.2. Available kernels: flashmla_sparse, flashmla_sparse_q8 (native FP8 e4m3 sparse prefill — no fp8→bf16 dequantization round-trip; Hopper SM90 + --kv-cache-dtype fp8_e4m3 only, prefill only), flashmla_kv, flashmla_auto, fa3 (Hopper only), tilelang (GPU/HPU/NPU), aiter (AMD, decode only), trtllm (Blackwell only). Defaults: Hopper BF16 KV → flashmla_sparse prefill / fa3 decode; Hopper FP8 KV → flashmla_kv both; Blackwell BF16 → flashmla_sparse / trtllm; Blackwell FP8 → trtllm both.
  • Index Cache: Reuses indexer results across layers for efficiency at negligible accuracy cost. For GLM-5 specifically, append --json-model-override-args '{"index_topk_pattern": "FFSFSSSFSSFFFSSSFFFSFSSSSSSFFSFFSFFSSFFFFFFSFFFFFSFFSSSSSSFSFFFSFSSSFSFFSFFSSS"}' for a better speed/accuracy tradeoff.
  • HiSparse (experimental): Reduces per-request GPU memory during long-context decode by offloading KV data to CPU pinned memory. Requires PD disaggregation mode (decode instance only). See HiSparse Guide.
  • NVFP4 on Blackwell: Specify --quantization modelopt_fp4 and --moe-runner-backend flashinfer_trtllm (recommended) / flashinfer_cutlass / flashinfer_cutedsl. Full example:
  • NCCL timeout: Slow model loading → add --dist-timeout 3600.

4. Model Invocation

4.1 Basic Usage

For basic API usage and request examples, please refer to:

4.2 Advanced Usage

4.2.1 Reasoning Parser

DeepSeek-V3.2 supports reasoning mode. Enable the reasoning parser during deployment to separate the thinking and content sections:
Command
Streaming with Thinking Process:
Example
Output Example:
Output
Note: The reasoning parser captures the model’s step-by-step thinking process, allowing you to see how the model arrives at its conclusions.

4.2.2 Tool Calling

DeepSeek-V3.2 and DeepSeek-V3.2-Exp support tool calling capabilities. But they use different parameters. Enable the tool call parser: Note: DeepSeek-V3.2-Speciale does NOT support tool calling. Launch it with reasoning parser only:
Command
Deployment Command: For DeepSeek-V3.2-Exp:
Command
For DeepSeek-V3.2, use --tool-call-parser deepseekv32 and remove --chat-template. Python Example (with Thinking Process):
Example
Output Example:
Output
Note:
  • The reasoning parser shows how the model decides to use a tool
  • Tool calls are clearly marked with the function name and arguments
  • You can then execute the function and send the result back to continue the conversation
Handling Tool Call Results:
Example

4.2.3 Multi-Token Prediction (EAGLE Speculative Decoding)

SGLang implements Multi-Token Prediction (MTP) for DeepSeek V3.2 based on EAGLE speculative decoding. This optimization significantly improves decoding speed for small batch sizes. With DP Attention:
Command
With Pure TP:
Command
Find optimal values for your workload with bench_speculative.py. The minimum viable config is --speculative-num-steps 1 --speculative-eagle-topk 1 --speculative-num-draft-tokens 2.
--max-running-requests defaults to 48 for MTP. Increase it for larger batch sizes.
The spec-v2 overlap scheduler is enabled by default. Pass --disable-overlap-schedule to disable.

4.2.4 PD Disaggregation

Prefill-Decode (PD) disaggregation separates prefill and decode stages onto different instances, improving GPU utilization for mixed workloads. Prefill command:
Command
Decode command:
Command
Router command:
Command
For production deployments (RBG / LWS-based, DeepEP EP parallelism), see multi_node_deployment docs.

4.2.5 DSA Long-Sequence Context Parallel and PP/CP

SGLang provides two context parallel (CP) modes for long-sequence workloads, controlled with --dsa-prefill-cp-mode. In-sequence splitting (--dsa-prefill-cp-mode in-seq-split): Each CP rank handles a uniform shard of the sequence; KV cache is gathered via all-gather. Batch size is restricted to 1 during prefill. See PR #12065.
Command
Round-robin splitting (--dsa-prefill-cp-mode round-robin-split, default): Distributes tokens by token_idx % cp_size. Supports fused MoE, FP8 KV cache, and multi-batch prefill. Cannot be combined with DP attention. See PR #13959.
Command
PP + CP (multi-node): Combines Pipeline Parallelism and Context Parallelism for cross-node scaling. The production-optimized configurations below have been verified on Hopper: We suggested DP2 + MTP for local deployment of agentic workflow with DeepSeek V3.2 on Hopper platform:
Command
CP + PP + EP + DP CP is currently enabled with PP=2 on Hopper platform and we can reduce TP=16 to TP=8 from standalone deployment:
Command
fp8 KV + CP + PP With FP8 KV, we can have less memory footprint. This can be combined with various parallel schemes:
Command

5. Benchmark

5.1 Speed Benchmark on Blackwell

Test Environment:
  • Hardware: NVIDIA B200 GPU (8x)
  • Model: DeepSeek-V3.2-Exp
  • Tensor Parallelism: 8
  • sglang version: 0.5.6
We use SGLang’s built-in benchmarking tool to conduct performance evaluation on the ShareGPT_Vicuna_unfiltered dataset. This dataset contains real conversation data and can better reflect performance in actual use scenarios. To simulate real-world usage patterns, we configure each request with 1024 input tokens and 1024 output tokens, representing typical medium-length conversations with detailed responses.

5.1.1 Latency-Sensitive Benchmark

  • Model Deployment Command:
Command
  • Benchmark Command:
Command
  • Test Results:
Output

5.1.2 Throughput-Sensitive Benchmark

  • Model Deployment Command:
Command
  • Benchmark Command:
Command
  • Test Results:
Output

5.2 Accuracy Benchmark

5.2.1 GSM8K Benchmark

  • Benchmark Command:
Command
  • Test Results:
    • DeepSeek-V3.2-Exp
  • Full GSM8K (1319 questions) — for a stricter accuracy check, run the full set 8-shot:
Command
  • 8-shot:
  • 20-shot (long-context; stays close to the 8-shot result):

5.2.2 MMLU Benchmark

  • Benchmark Command:
Command
  • Test Results:
    • DeepSeek-V3.2-Exp

5.2.3 GPQA-Diamond Benchmark

  • Benchmark Command:
Command
  • Test Results (model: deepseek-ai/DeepSeek-V3.2-Exp, 8×B200):
    • Default (temperature=0): mean 0.797 over 8 runs — closely matches the official GPQA-Diamond score of 79.9 for DeepSeek-V3.2-Exp reported in its model card
    • With temperature=1.0, top_p=0.95 (as recommended by DeepSeek):
Command

5.2.4 AIME 2025 Benchmark

Results on AIME 2025 (8×B200), evaluated with NeMo-Skills:
Modelpass@1 avg-of-4majority@4pass@4
DeepSeek-V3.2-Exp87.50% ± 1.67%90.00%90.00%
DeepSeek-V3.292.50% ± 1.67%94.71%96.67%
DeepSeek-V3.2-Speciale95.00% ± 1.92%95.83%100.00%
Reproduction. Install NeMo-Skills, launch the server with the tool-call and reasoning parsers, then run ns eval:
Command

5.3 Speed Benchmark on Hopper

Test Environment:
  • Hardware: NVIDIA H800 GPU (16x)
  • Model: DeepSeek-V3.2
  • Tensor Parallelism: 16
  • sglang version: 0.5.9

5.3.1 Latency-Sensitive Benchmark

  • Model Deployment Command:
Command
  • Benchmark Command:
Command
  • Test Results:
Output

5.3.2 Throughput-Sensitive Benchmark

We simply use the same deployment method and vary the throughput by maximizing concurrencies:
Command
DeepSeek 3.2 can steadily support concurrency up to 1024 and when concurrency is greater than 128, the TTFT increase sharply: DeepSeek V3.2 Concurrency ISL/OSL=1024/128 Performance record:
Output
By adding --random-range-ratio 1, we could get even higher statistical numbers:
Output