Skip to main content

Deployment

Command
The image ships with mistral-common 1.13.0 or later, required to load the checkpoints’ tekken.json. For how to launch it, see Install → Method 3: Using Docker. Substitute the inner sglang serve ... with what the command generator below produces.
Pick your hardware to generate the launch command:
  • Low Latency — fastest reply for a single user, with DSpark speculative decoding from the draft bundled in the checkpoint. Pick for chat.
  • High Throughput — most tokens per second across many users, without speculative decoding. Best for batch jobs.
The verified recipes are FP8 at TP8 on 8× B300, NVFP4 at TP4 on 4× GB300, and on Vera Rubin (arm64) FP8 at TP8 across two 4-GPU trays or NVFP4 at TP4 on one tray. Commands for other GPUs are badged Not Verified; combinations without a command explain why in the panel. Every command carries --reasoning-parser auto --tool-call-parser auto: without them, reasoning and tool calls come back as raw text in content.

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.

1. Model Introduction

Mistral Large 4 is Mistral AI’s 1T-parameter Mixture-of-Experts model with 52B active parameters and a vision encoder. It has 72 layers with 128 routed experts (top-4) plus one shared expert, multi-head latent attention with DSA sparse attention, and cross-layer KV sharing. The checkpoints declare a native 1,048,576-token context and bundle a DSpark draft model for speculative decoding.
CheckpointWeightsHardware
mistralai/Mistral-Large-4-1T-A52BFP8 E4M3, 128×128 block scales8× B300, two Vera Rubin trays
mistralai/Mistral-Large-4-1T-A52B-NVFP4NVFP4 routed experts, block-FP8 attention and dense layersBlackwell only: 4× GB300, one Vera Rubin tray
Recommended generation: temperature=1.0, top_p=0.95 (the checkpoint’s generation_config.json defaults; informational — do not hardcode in client code). License: Mistral Ecosystem Open-Weight License; see the model card. Resources: HuggingFace FP8 and NVFP4.

2. Benchmarks

Accuracy uses sgl-eval at temperature 1.0, top-p 0.95, at most 8,192 output tokens and reasoning_effort low, unless noted. Speed uses bench_serving with 1,024-token random prompts and 512 output tokens, 64 requests per concurrency point and a flushed cache; total tok/s/GPU counts input and output tokens. The benchmark card of each recipe carries the full protocol and a ⚡ Reproduce button.
HardwareRecipeResult
8× B300FP8, TP8, FP8 KVGSM8K 96.74% (1,319 questions, all stopped); 774 total tok/s/GPU at concurrency 64
8× B300FP8, TP8, DSpark3.71 accepted tokens per 4-token verify step; 1,018 total tok/s/GPU at concurrency 64
4× GB300NVFP4, TP4GSM8K, first 100 questions: 98% at low, 97–98% at high; MMMU-Pro 72.43% (seed 1); 1,560 total tok/s/GPU at concurrency 64
4× GB300NVFP4, TP4, DSpark3.69 accepted tokens per 4-token verify step; 2,812 total tok/s/GPU at concurrency 64
Vera Rubin, two traysFP8, TP8, BF16 KVGSM8K 96.64%, MMLU 91.70%, MMMU-Pro 72.22% (mean of 3 seeds)
Vera Rubin, one trayNVFP4, TP4, BF16 KVGSM8K 96.74%, MMLU 91.64%, MMMU-Pro 72.66% (mean of 3 seeds)

3. Configuration Tips

  • Parsers. auto resolves to the mistral reasoning and tool-call parsers; --reasoning-parser mistral --tool-call-parser mistral is equivalent. Without a reasoning parser the reasoning stays inline in content as [THINK]…[/THINK]; without a tool-call parser tool calls come back as [TOOL_CALLS]… text.
  • Tokenizer. By default the server tokenizes with the checkpoint’s tokenizer.json and renders chat_template.jinja, which is token-identical to mistral-common for chat prompts. --tokenizer-mode mistral tokenizes through mistral-common instead. Either way mistral-common 1.13.0 or later is required: earlier versions cannot load the checkpoints’ tekken.json.
  • Context and KV cache. Leave --context-length unset for the native 1,048,576 tokens. The KV cache defaults to FP8 (E4M3) on Blackwell and Vera Rubin and BF16 on Hopper; on 8× B300 at --mem-fraction-static 0.85 the FP8 KV pool holds about 2.49M tokens, and about 1.34M with --kv-cache-dtype bfloat16.
  • DSpark. The server loads the bundled draft from the checkpoint (3 drafted tokens, 4-token verify step); do not pass --speculative-draft-model-path or draft-length flags. With speculative decoding --max-running-requests defaults to 48. For bursts of short requests, --max-running-requests 64 raises throughput (the GB300 Low Latency recipe sets it); keep 48 or lower for long-context traffic.
  • Long prompts. Prefill CP 2 (Playground → Attention → Prefill CP) on top of the Low Latency recipe lowers long-prompt TTFT at a small decode cost.
  • KV capacity. Decode Context Parallel (DCP) and HiSparse in the Playground hold more tokens at a decode-throughput cost. Neither combines with prefill CP.
  • Vera Rubin. The generated commands carry the environment variables of the measured runs; tokenizer, context and KV dtype resolve from the checkpoint like on other hardware. The mistral-large-4 image is multi-arch (amd64 + arm64).

4. Advanced Usage

4.1 Reasoning

The reasoning comes back in reasoning_content and the answer in content. reasoning_effort accepts low, medium and high; a request that omits it reasons at the checkpoint default, high, and "none" returns HTTP 400.
Example
Output

4.2 Image Input

Images go in OpenAI-style image_url content parts, as URLs or base64 data URLs.
Example
Output

4.3 Tool Calling

Function calls come back as structured tool_calls with finish_reason tool_calls.
Example
Output

5. Known Limitations

  • Pipeline parallelism must keep layer 35 and the layers that read its KV cache on one stage (SGLANG_PP_LAYER_PARTITION=35,37 for two stages). DSpark accepts pipeline parallelism only on a PD prefill server.
  • PD disaggregation runs with a peer-config fingerprint guard; a 1P1D setup (one prefill and one decode server) is validated end to end.
  • Prefill CP with DCP is unsupported; the server rejects the combination at startup.
  • KV-cache sharding (--enable-kv-cache-sharding) is unsupported with the model’s cross-layer KV sharing; the server rejects it at startup.