Skip to main content

1. Model Introduction

Devstral 2 is an agentic LLM family for software engineering tasks. It is designed for agentic workflows such as tool use, codebase exploration, and multi-file edits, and achieves strong performance on SWE-bench. The Devstral 2 Instruct checkpoints are instruction-tuned FP8 models, making them a good fit for chat, tool-using agents, and instruction-following SWE workloads. Key Features:
  • Agentic coding: Optimized for tool-driven coding and software engineering agents
  • Improved performance: A step up compared to earlier Devstral models
  • Better generalization: More robust across diverse prompts and coding environments
  • Long context: Up to a 256K context window
Use Cases: AI code assistants, agentic coding, and software engineering tasks that require deep codebase understanding and tool integration. For enterprises requiring specialized capabilities (increased context, domain-specific knowledge, etc.), please reach out to Mistral. Models:

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.
Devstral 2 requires a recent transformers. Please verify transformers >= 5.0.0.rc:
Command
If your version is lower, upgrade:
Command

3. Model Deployment

3.1 Basic configuration

Interactive Command Generator: Use the configuration selector below to generate a launch command for Devstral Small 2 (24B) or Devstral 2 (123B).
The TP size is set to the minimum required for the selected model size.

3.2 Configuration tips

  • Context length vs memory: Devstral 2 advertises a long context window; if you are memory-constrained, start by lowering --context-length (for example 32768) and increase once things are stable.
  • FP8 checkpoints: Both Devstral Small 2 and Devstral 2 are published as FP8 weights. If you hit kernel / dtype issues, try a newer SGLang build and recent CUDA drivers.

4. Model Invocation

4.1 Basic Usage (OpenAI-Compatible API)

SGLang exposes an OpenAI-compatible endpoint. Example:
Example
Output Example:
Output

4.2 Tool calling (optional)

Devstral 2 supports tool calling capabilities. Enable the tool call parser:
Command
Python Example (with Thinking Process):
Example
Output Example:
Output

AMD GPU Support

1. Model Deployment

This section provides deployment configurations optimized for different hardware platforms and use cases.

1.1 Basic Usage

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

1.2 Advanced Usage

Command

2.Benchmark

5.1 Benchmark Commands

Scenario 1: Chat (1K/1K) - Most Important
  • Model Deployment
Command
  • Low Concurrency (Latency-Optimized)
Command
Output
  • Medium Concurrency (Balanced)
Command
Output
  • High Concurrency (Throughput-Optimized)
Command
Output

5.2 Understanding the Results

Key Metrics:
  • Request Throughput (req/s): Number of requests processed per second
  • Output Token Throughput (tok/s): Total tokens generated per second
  • Mean TTFT (ms): Time to First Token - measures responsiveness
  • Mean TPOT (ms): Time Per Output Token - measures generation speed
  • Mean ITL (ms): Inter-Token Latency - measures streaming consistency
Why These Configurations Matter:
  • 1K/1K (Chat): Represents the most common conversational AI workload. This is the highest priority scenario for most deployments.
  • 1K/8K (Reasoning): Tests long-form generation capabilities crucial for complex reasoning, code generation, and detailed explanations.
  • 8K/1K (Summarization): Evaluates performance with large context inputs, essential for RAG systems, document Q&A, and summarization tasks.
  • Variable Concurrency: Captures the Pareto frontier - the optimal trade-off between throughput and latency at different load levels. Low concurrency shows best-case latency, high concurrency shows maximum throughput.
Interpreting Results:
  • Compare your results against baseline numbers for your hardware
  • Higher throughput at same latency = better performance
  • Lower TTFT = more responsive user experience
  • Lower TPOT = faster generation speed

5.3 Accuracy Benchmark

Document model accuracy on standard benchmarks:

5.3.1 GSM8K Benchmark

  • Benchmark Command
Command
Test Results:
Output