Running gpt-oss-120b on H200
Quick answer
gpt-oss-120b sustains 9,319 tokens/s per GPU on H200 at 50 tokens/s per user, which works out to $0.036 per million tokens at hyperscaler pricing, served by vLLM. Fastest measured TTFT: 0.0 ms; fastest TPOT: 0.0 ms (each the best across all configs, not one run).
Benchmarked configs
101
Serving engines
TRTLLM, vLLM
Precisions
fp4
Run dates
2025-12-15 → 2026-05-30
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 | 12,300 | $0.028 | vLLM | fp4 |
| 50 tok/s | 9,319 | $0.036 | vLLM | fp4 |
| 75 tok/s | 7,422 | $0.046 | vLLM | fp4 |
| 100 tok/s | 6,346 | $0.053 | vLLM | fp4 |
| 150 tok/s | 4,384 | $0.077 | vLLM | fp4 |
| 200 tok/s | 2,845 | $0.12 | vLLM | fp4 |
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.22 | $0.036 |
| Neocloud | $1.59 | $0.047 |
| Retail | $2.05 | $0.061 |
Frequently asked questions
- How fast is gpt-oss-120b on H200?
- At an interactivity target of 50 tokens/s per user on a single-turn chat workload (8k input / 1k output), H200 sustains 9,319 tokens/s per GPU serving gpt-oss-120b with vLLM in FP4. Peak measured throughput across all configs is 13,091 tokens/s per GPU.
- How much does it cost to serve gpt-oss-120b on H200?
- $0.036 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 gpt-oss-120b on H200?
- The runs behind this page used TRTLLM, vLLM in FP4. Engines are rebuilt and re-benchmarked continuously, so the best config can change between visits.
- How are these gpt-oss-120b numbers measured?
- Every number is measured on real H200 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-05-30. The same derivation powers the InferenceX overview leaderboard.