Skip to main content

1. Model Introduction

GLM-4.5 is a powerful language model developed by Zhipu AI, featuring advanced capabilities in reasoning, function calling, and multi-modal understanding. Key Features:
  • Advanced Reasoning: Built-in reasoning capabilities for complex problem-solving
  • Multiple Quantizations: BF16 and FP8 variants for different performance/memory trade-offs
  • Hardware Optimization: Specifically tuned for AMD MI300X/MI325X/MI355X GPUs
  • High Performance: Optimized for both throughput and latency scenarios
Available Models: License: Please refer to the official GLM-4.5 model card for license details.

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.

3. Model Deployment

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

3.1 Basic Configuration

Interactive Command Generator: Use the configuration selector below to automatically generate the appropriate deployment command for your hardware platform, quantization method, deployment strategy, and thinking capabilities.

3.2 Configuration Tips

  • EAGLE Speculative Decoding: Supported for GLM-4.5/4.6. Add --speculative-algorithm EAGLE --speculative-num-steps 3 --speculative-eagle-topk 1 --speculative-num-draft-tokens 4. The spec-v2 overlap scheduler is enabled by default; pass --disable-overlap-schedule to disable.
  • Thinking Budget: Use --enable-custom-logit-processor flag and pass Glm4MoeThinkingBudgetLogitProcessor in requests to cap the model’s thinking token count (see section 4.2.3).

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

GLM-4.5 supports Thinking mode by default. Enable the reasoning parser during deployment to separate the thinking and the 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

Parser names by model: GLM-4.5 and GLM-4.6 use --tool-call-parser glm45. GLM-4.7 and GLM-4.7-Flash use --tool-call-parser glm47. All GLM models use --reasoning-parser glm45 regardless of generation.
GLM-4.5 supports tool calling capabilities. Enable the tool call parser:
Command
Python Example (with Thinking Process):
Example
Output Example:
Output

4.2.3 Thinking Budget

Limit the number of thinking tokens using CustomLogitProcessor. Launch with --enable-custom-logit-processor:
Example

5. Benchmark

This section uses industry-standard configurations for comparable benchmark results.

5.1 Speed Benchmark

Test Environment:
  • Hardware: AMD MI300X (8x), AMD MI325X (8x), AMD MI355X (8x)
  • Model: GLM-4.5
  • Tensor Parallelism: 8
  • SGLang Version: 0.5.6.post1
Benchmark Methodology: We use industry-standard benchmark configurations to ensure results are comparable across frameworks and hardware platforms.

5.1.1 Standard Test Scenarios

Three core scenarios reflect real-world usage patterns:
ScenarioInput LengthOutput LengthUse Case
Chat1K1KMost common conversational AI workload
Reasoning1K8KLong-form generation, complex reasoning tasks
Summarization8K1KDocument summarization, RAG retrieval

5.1.2 Concurrency Levels

Test each scenario at three concurrency levels to capture the throughput vs. latency tradeoff (Pareto frontier):
  • Low Concurrency: --max-concurrency 1 (Latency-optimized)
  • Medium Concurrency: --max-concurrency 16 (Balanced)
  • High Concurrency: --max-concurrency 100 (Throughput-optimized)

5.1.3 Number of Prompts

For each concurrency level, configure num_prompts to simulate realistic user loads:
  • Quick Test: num_prompts = concurrency × 1 (minimal test)
  • Recommended: num_prompts = concurrency × 5 (standard benchmark)
  • Stable Measurements: num_prompts = concurrency × 10 (production-grade)

5.1.4 Benchmark Commands

Scenario 1: Chat (1K/1K) - Most Important
  • Model Deployment
Command
  • Low Concurrency (Latency-Optimized)
Command
  • Medium Concurrency (Balanced)
Command
  • High Concurrency (Throughput-Optimized)
Command
Scenario 2: Reasoning (1K/8K)
  • Low Concurrency
Command
  • Medium Concurrency
Command
  • High Concurrency
Command
Scenario 3: Summarization (8K/1K)
  • Low Concurrency
Command
  • Medium Concurrency
Command
  • High Concurrency
Command

5.1.5 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 tradeoff 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.2 Accuracy Benchmark

Document model accuracy on standard benchmarks:

5.2.1 GSM8K Benchmark

  • Benchmark Command
Command