Deployment
Install SGLang
Install SGLang
Install from a source checkout that includes the K2 Horizon runtime support in PR #37654 before using the generated commands:For general source-install guidance, see Install → Method 2: From source.
Command
Playground
The base recipes enable thek2_horizon reasoning parser. Use the Playground to configure the k2_horizon tool-call parser, TP and MoE expert-parallel overrides, NGRAM speculative decoding, PD disaggregation, and HiCache. A separate validation pass functionally exercised the tool-call parser on all six checkpoints; every other Playground override remains unverified.
1. Model introduction
K2 Horizon is an IFM model family spanning six checkpoints from 0.9B to 375B parameters. The family includes dense models, Mixture-of-Experts models, and the 36B checkpoint’s routed Mixture-of-Value-Attention path. This page provides native SGLang serving recipes for the family.| Checkpoint | Architecture | Context length | H200 recipe |
|---|---|---|---|
| 0.9B | Dense | 131,072 | BF16 · TP1 |
| 3.7B | Dense | 524,288 | BF16 · TP1 |
| 7B | Dense | 524,288 | BF16 · TP1 |
| 32B | Dense | 524,288 | BF16 · TP2 |
| 36B | MoE + MoVA | 524,288 | BF16 · TP2 |
| 375B | MoE | 524,288 | BF16 · TP8 |
All six checkpoints use the Apache License 2.0.
2. Configuration tips
- Hardware and precision: The current matrix covers NVIDIA H200 GPUs and BF16 checkpoints only.
- Parallelism: Use TP1 for 0.9B, 3.7B, and 7B; TP2 for 32B and 36B; and TP8 for 375B. Each recipe stays within one node.
- Attention: The verified base recipes select FlashAttention-3 with
--attention-backend fa3. - Revisions: The recipes pin revisions
9b9ec1f7e17f62ed218df542687a144116219d84(0.9B),c177771836a4c460743c00002c22483f6f18d1eb(3.7B),69ada542b68fe13d767479db2ab9421baff88681(7B),e1fd0277713e4eefcd3416348fd6fedacf7f2392(32B),16d20c739c687c08423422d1a2fbba6c529014cd(36B), and12812264242a14dce44aa7ae27f931ff4584bcbf(375B). - Parsers: The base recipes enable reasoning with
--reasoning-parser k2_horizon. Enable--tool-call-parser k2_horizonfrom the Parsers card in the Playground when you need tool calling. - 36B router provenance: The 36B checkpoint’s source xLLM router used two GEMM partitions.
--json-model-override-args '{"xllm_source_router_gemm_partitions":2}'preserves its BF16 partial-GEMM rounding and FP32 reduction order; SGLang does not infer this source topology from runtime TP. - 375B loading: The 375B recipe disables multithreaded weight loading with
--model-loader-extra-config '{"enable_multithread_load":false}'. - Playground features: TP, EP, NGRAM, PD disaggregation, and HiCache are optional, unverified command overrides. The tool-call parser was functionally exercised separately.
- Deliberate omissions: Context parallelism is unsupported or unvalidated for xLLM. DP-attention and alternate MoE backend selectors are not exposed until they are validated.
- Validation: All six recipes completed native speed and full GSM8K evaluation on H200 using the K2 Horizon runtime support in PR #37654.
- 375B provenance: The 375B benchmark launched a directly mounted checkpoint and passed revision
12812264242a14dce44aa7ae27f931ff4584bcbfto the server. The other five launches used materialized Hugging Face snapshots at their pinned revisions.
3. Benchmark results
Speed was measured with nativesglang.benchmark.serving using fixed random token IDs: 8,192 input tokens, 1,024 output tokens, 64 warmup requests, a cache flush, and seed 20260901. The latency run used 32 prompts at concurrency 1. The throughput run used 256 prompts at concurrency 64 for TP1, 32 for TP2, and 8 for TP8. TTFT and TPOT are medians within each launch; the benchmark cards show the arithmetic mean across the two launches. Throughput per GPU is (total input tokens + total output tokens) / duration / TP.
GSM8K used the full 1,319-example test split with sgl-eval, 32 client threads, a 32,768-token output limit, temperature 0, top-p 0.95, seed 0, and high reasoning effort. The mean and both independent server-launch scores are shown below. All requests completed without errors. Responses that reached the output limit remain in the score: truncation was 6.90% in both 0.9B launches, 4.09% and 4.70% for 3.7B, and at most 1.14% for the other checkpoints.
4. Advanced usage
4.1 Reasoning
The base recipes include--reasoning-parser k2_horizon. The parser returns thinking in reasoning_content and the final answer in content.
The example output below was captured with the 3.7B checkpoint and both parser flags enabled.
Reasoning example (Python)
Reasoning example (Python)
Example
Example Output
Example Output
Output
4.2 Tool calling
Enable Tool Call Parser in the Parsers card of the Playground to add--tool-call-parser k2_horizon. The parser exposes K2 tool output as OpenAI-compatible message.tool_calls.
The example output below was captured with the 32B checkpoint and both parser flags enabled.
Tool-calling example (Python)
Tool-calling example (Python)
Example
Example Output
Example Output
Output
