MulaiPapan peringkatDecode calculatorModelOrganizationsReportsMatrix runsHardwareTolok UkurMarketplaceSewaProDokumen API
Bahasa
Actual Computer — Every computer, one endpoint

Speed test matrix

Qwen3.8-Flash-Next on H200 SXM 141GB ×4

vllm · 0.1.1.dev5+ge77daef89 · BF166 contexts (8K–251K) × 8 concurrency levels (1–128) · prefill at 8K, 16K, 32K, 64K, 128K, 251K, 256K
by @keennaylmx dev importMeasured

Hardware

Type
Discrete GPU
GPU
H200 SXM
GPU count
4
VRAM
564 GB (4 × 141 GB)
OS
linux

Engine

Engine
vllm
Version
0.1.1.dev5+ge77daef89
Quantization
BF16
Backend
cuda
Build
cuda-13.2
Commit
e77daef89e18

Run

Served model
qwen
Revision
main
Decode test
Fixed duration
Prefill mode
Measured during decode warm-up
Time per measurement
30 s
Max output
4,096 tokens

Launch command

"$HOME/env_h200-qwen-flash-next-vllm/bin/vllm" serve Qwen/Qwen3.8-Flash-Next --served-model-name qwen --tensor-parallel-size 4 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder --max-model-len 262144 --gpu-memory-utilization 0.84 --host 0.0.0.0 --port 8000 --api-key <redacted> --dtype bfloat16 --enable-expert-parallel --engram-config '{"cpu_offload":false}' --speculative-config '{"method":"mtp","num_speculative_tokens":1}'

Prefill

prompt tok/s by context length
8K context24.9K329 ms TTFT
16K context29.9K540 ms TTFT
32K context33.5K960 ms TTFT
64K context34.8K1,841 ms TTFT
128K context34.8K3,679 ms TTFT
251K context32.7K7,679 ms TTFT
256K context32.1K7,969 ms TTFT

Sustained decode

total tok/s · rows are context length, columns are simultaneous requests
Context1248163264128
8K224.5158 ms TTFT399.2173 ms TTFT689.1833 ms TTFT1,140.4294 ms TTFT1,946.4423 ms TTFT3,250.02,420 ms TTFT5,273.71,291 ms TTFT7,931.52,188 ms TTFT
16K228.4169 ms TTFT405.8194 ms TTFT692.1311 ms TTFT1,142.7341 ms TTFT1,935.0467 ms TTFT3,252.7947 ms TTFT5,276.91,425 ms TTFTOver capacity
32KLooped399.6224 ms TTFT691.5224 ms TTFT1,136.0361 ms TTFT1,936.6845 ms TTFT3,221.91,326 ms TTFTOver capacityOver capacity
64K226.6282 ms TTFT395.7306 ms TTFT689.5395 ms TTFT1,136.7506 ms TTFT1,914.41,237 ms TTFTOver capacityOver capacityOver capacity
128K217.3451 ms TTFT400.7544 ms TTFT688.2527 ms TTFT1,119.31,080 ms TTFTOver capacityOver capacityOver capacityOver capacity
251K219.7907 ms TTFT405.11,030 ms TTFT678.3966 ms TTFTOver capacityOver capacityOver capacityOver capacityOver capacity

Looped: the model kept repeating the same text, so the benchmark discarded this measurement. Over capacity: not run because this many requests at this context would exceed the server's KV cache.

TTFT is measured after the benchmark warms the server's prompt cache, so it mostly excludes prefill.

All measurements

Latencies are medians. Total tok/s is output across all simultaneous requests.
PhaseContextRequests at onceStatusTotal tok/sPer request tok/sTTFTTime between tokensAverage active requestsCompleted requestsOutput tokensMeasured for
Prefill8K1Valid24.9K—329 ms——1——
Prefill16K1Valid29.9K—540 ms——1——
Prefill32K1Valid33.5K—960 ms——1——
Prefill64K1Valid34.8K—1,841 ms——1——
Prefill128K1Valid34.8K—3,679 ms——1——
Prefill251K1Valid32.7K—7,679 ms——1——
Prefill256K1Valid32.1K—7,969 ms——1——
Sustained decode8K1Valid224.5226.6158 ms4.4 ms1.016,73430.0 s
Sustained decode8K2Valid399.2198.9173 ms5.0 ms2.0211,97630.0 s
Sustained decode8K4Valid689.1176.4833 ms5.7 ms4.0420,67430.0 s
Sustained decode8K8Valid1,140.4131.2294 ms7.6 ms8.0834,20830.0 s
Sustained decode8K16Valid1,946.4117.0423 ms8.6 ms16.0358,37930.0 s
Sustained decode8K32Valid3,250.0100.32,420 ms10.0 ms32.0097,49830.0 s
Sustained decode8K64Valid5,273.774.31,291 ms13.5 ms64.00158,17430.0 s
Sustained decode8K128Valid7,931.560.02,188 ms16.7 ms128.00238,08530.0 s
Sustained decode16K1Valid228.4229.1169 ms4.4 ms1.016,85030.0 s
Sustained decode16K2Valid405.8203.0194 ms4.9 ms2.0212,17330.0 s
Sustained decode16K4Valid692.1175.2311 ms5.7 ms4.0420,76330.0 s
Sustained decode16K8Valid1,142.7142.0341 ms7.0 ms7.9834,27930.0 s
Sustained decode16K16Valid1,935.0120.7467 ms8.3 ms16.0658,03430.0 s
Sustained decode16K32Valid3,252.7101.2947 ms9.9 ms32.0097,54030.0 s
Sustained decode16K64Valid5,276.981.21,425 ms12.3 ms64.00158,26330.0 s
Sustained decode16K128Over capacity————————
Sustained decode32K1Looped—————00—
Sustained decode32K2Valid399.6199.9224 ms5.0 ms2.0211,98630.0 s
Sustained decode32K4Valid691.5173.0224 ms5.8 ms4.0420,74530.0 s
Sustained decode32K8Valid1,136.0141.5361 ms7.1 ms8.0834,07030.0 s
Sustained decode32K16Valid1,936.6119.8845 ms8.3 ms16.0457,85829.9 s
Sustained decode32K32Valid3,221.999.21,326 ms10.1 ms32.0096,62130.0 s
Sustained decode32K64Over capacity————————
Sustained decode32K128Over capacity————————
Sustained decode64K1Valid226.6229.4282 ms4.4 ms1.016,79730.0 s
Sustained decode64K2Valid395.7200.5306 ms5.0 ms2.0211,87030.0 s
Sustained decode64K4Valid689.5173.1395 ms5.8 ms4.0420,68230.0 s
Sustained decode64K8Valid1,136.7142.0506 ms7.0 ms7.9834,09430.0 s
Sustained decode64K16Valid1,914.4117.81,237 ms8.5 ms16.0457,22429.9 s
Sustained decode64K32Over capacity————————
Sustained decode64K64Over capacity————————
Sustained decode64K128Over capacity————————
Sustained decode128K1Valid217.3221.1451 ms4.5 ms1.016,51830.0 s
Sustained decode128K2Valid400.7204.4544 ms4.9 ms1.9212,02030.0 s
Sustained decode128K4Valid688.2174.5527 ms5.7 ms3.9420,64430.0 s
Sustained decode128K8Valid1,119.3141.61,080 ms7.1 ms7.9833,57030.0 s
Sustained decode128K16Over capacity————————
Sustained decode128K32Over capacity————————
Sustained decode128K64Over capacity————————
Sustained decode128K128Over capacity————————
Sustained decode251K1Valid219.7227.1907 ms4.4 ms1.016,58930.0 s
Sustained decode251K2Valid405.1208.91,030 ms4.8 ms2.0212,15030.0 s
Sustained decode251K4Valid678.3175.9966 ms5.7 ms3.9420,34630.0 s
Sustained decode251K8Over capacity————————
Sustained decode251K16Over capacity————————
Sustained decode251K32Over capacity————————
Sustained decode251K64Over capacity————————
Sustained decode251K128Over capacity————————

Looped: the model kept repeating the same text, so the benchmark discarded this measurement. Over capacity: not run because this many requests at this context would exceed the server's KV cache.