Running Qwen3.5 on H100
Quick answer
Qwen3.5 sustains 1,584 tokens/s per GPU on H100 at 50 tokens/s per user, which works out to $0.21 per million tokens at hyperscaler pricing, served by SGLang. Fastest measured TTFT: 0.3 ms; fastest TPOT: 0.0 ms (each the best across all configs, not one run).
Benchmarked configs
35
Serving engines
SGLang
Precisions
fp8
Run dates
2026-07-05 → 2026-08-07
Throughput at every interactivity target
Serving is a trade-off: push more concurrent users through a GPU and each user's tokens arrive slower. The ladder below reads the measured frontier at each per-user speed target on a single-turn chat workload (8k input / 1k output), using the best engine and precision at that point.
| Per-user target | Tokens/s per GPU | $ / 1M tokens | Engine | Precision |
|---|---|---|---|---|
| 30 tok/s | 2,473 | $0.13 | SGLang | fp8 |
| 50 tok/s | 1,584 | $0.21 | SGLang | fp8 |
| 75 tok/s | 1,302 | $0.25 | SGLang | fp8 |
| 100 tok/s | 1,079 | $0.30 | SGLang | fp8 |
| 150 tok/s | 775 | $0.42 | SGLang | fp8 |
| 200 tok/s | - | - | SGLang | fp8 |
What serving actually costs
Converting the 50 tokens/s per user operating point to $ per million total tokens across rental pricing tiers from the SemiAnalysis AI Cloud TCO model.
| Pricing tier | $ / GPU / hr | $ / 1M tokens |
|---|---|---|
| Hyperscaler | $1.17 | $0.21 |
| Neocloud | $1.55 | $0.27 |
| Retail | $1.78 | $0.31 |
Frequently asked questions
- How fast is Qwen3.5 on H100?
- At an interactivity target of 50 tokens/s per user on a single-turn chat workload (8k input / 1k output), H100 sustains 1,584 tokens/s per GPU serving Qwen3.5 with SGLang in FP8. Peak measured throughput across all configs is 4,198 tokens/s per GPU.
- How much does it cost to serve Qwen3.5 on H100?
- $0.21 per million total tokens at hyperscaler $/GPU/hr pricing, at 50 tokens/s per user. Neocloud and retail rental tiers are tabulated above; slower interactivity targets lower the cost further.
- Which serving engines run Qwen3.5 on H100?
- The runs behind this page used SGLang in FP8. Engines are rebuilt and re-benchmarked continuously, so the best config can change between visits.
- How are these Qwen3.5 numbers measured?
- Every number is measured on real H100 hardware by the InferenceX fleet, sweeping concurrency on a single-turn chat workload (8k input / 1k output) to trace the throughput-versus-interactivity frontier; the newest run landed on 2026-08-07. The same derivation powers the InferenceX overview leaderboard.