Erste SchritteLeaderboardDecode calculatorModelleOrganizationsReportsMatrix runsHardwareBenchmarksMarktplatzVermietungenProAPI-Doku
Sprache
Actual Computer — Every computer, one endpoint

Speed test matrix

Qwen3.8-Flash-Next-W4A16-AutoRound on CMP 170HX 64GB ×2

vllm · 0.30.0 · W4A166 contexts (0–248K) × 8 concurrency levels (1–128) · prefill at 8K, 16K, 32K, 64K, 128K
by @Sandbergllm-inference-bench v0.8.0Measured

Hardware

Type
Discrete GPU
GPU
CMP 170HX
GPU count
2
VRAM
64 GB (2 × 32 GB)
CPU
2x Intel Xeon E5-2630 v3
RAM
64 GB
OS
Ubuntu 26.04.1

Engine

Engine
vllm
Version
0.30.0
Quantization
W4A16
Backend
cuda
Build
ghcr.io/alexbrandes/cmp170hx-qwen38-flash-next@sha256:d6fc872d943b3e9e5cc9eb583b51d72af200e039fbbb7401700bb38d665f0957

Run

Served model
qwen3.8-flash-next-w4a16
Revision
main
Decode test
Fixed duration
Prefill mode
Measured during decode warm-up
Time per measurement
30 s
Max output
8,192 tokens

Launch command

# Published recipe run as-is: AlexBrandes' cmp170hx-qwen38-flash-next (github.com/AlexBrandes/cmp170hx-qwen38-flash-next @ c0db9613d1) on its pinned engine image. Thank you AlexBrandes for the recipe and engine fork, and Intel for the W4A16 AutoRound checkpoint (rev 4c67bf68). Only the port and local paths were set, and the recipe's optional host tune was skipped so the cards stay at our 180 W cap (the recipe sets 170 W). Spec decode: MTP, 5 tokens lookahead
# 2x NVIDIA CMP 170HX 64GB (cmpunlocker), 180 W limit each, PCIe Gen2 x4 links | 2x Intel Xeon E5-2630 v3 | 64 GB DDR4 | Ubuntu 26.04.1, NVIDIA driver 610.57.04
git clone https://github.com/AlexBrandes/cmp170hx-qwen38-flash-next && cd cmp170hx-qwen38-flash-next && git checkout c0db9613d1 && HOST_TUNE=0 ./start.sh
# start.sh launches: vllm serve Qwen3.8-Flash-Next-W4A16-AutoRound --pipeline-parallel-size 2 (VLLM_PP_LAYER_PARTITION=26,22) --max-model-len 262144 --block-size 1680 --mamba-cache-mode align --mamba-ssm-cache-dtype float32 --max-num-seqs 8 --max-num-batched-tokens 2048 --gpu-memory-utilization 0.95 --enable-prefix-caching -cc=<config/compilation.json> --speculative-config {"method":"mtp","num_speculative_tokens":5} (int4 draft head)

Prefill

prompt tok/s by context length
8K context5,4941,492 ms TTFT
16K context5,8502,765 ms TTFT
32K context5,9975,363 ms TTFT
64K context6,13510,452 ms TTFT
128K context6,13220,883 ms TTFT

Sustained decode

total tok/s · rows are context length, columns are simultaneous requests
Context1248163264128
070.41,495 ms TTFT110.6431 ms TTFT170.4673 ms TTFT298.8731 ms TTFT305.3Requests queued783 ms TTFT311.0Requests queued842 ms TTFT313.0Requests queued959 ms TTFT293.4Requests queued1,165 ms TTFT
16K66.8736 ms TTFT119.41,156 ms TTFT153.41,632 ms TTFT287.82,781 ms TTFT286.2Requests queued2,784 ms TTFT282.1Requests queued2,927 ms TTFTOver capacityOver capacity
32K64.5726 ms TTFT120.11,099 ms TTFT168.11,663 ms TTFT297.12,478 ms TTFT296.4Requests queued2,627 ms TTFTOver capacityOver capacityOver capacity
64K70.1829 ms TTFT121.11,358 ms TTFT173.12,017 ms TTFT290.42,999 ms TTFTOver capacityOver capacityOver capacityOver capacity
128K72.11,340 ms TTFT108.51,677 ms TTFT165.42,450 ms TTFT308.43,818 ms TTFTOver capacityOver capacityOver capacityOver capacity
248K82.61,997 ms TTFT105.92,975 ms TTFT176.34,370 ms TTFTOver capacityOver capacityOver capacityOver capacityOver capacity

Requests queued: the server could not run all requests at once, so some waited in a queue. 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
Prefill8K1Valid5,494.0—1,492 ms——1——
Prefill16K1Valid5,850.0—2,765 ms——1——
Prefill32K1Valid5,997.0—5,363 ms——1——
Prefill64K1Valid6,135.0—10,452 ms——1——
Prefill128K1Valid6,132.0—20,883 ms——1——
Sustained decode01Valid70.470.91,495 ms14.1 ms1.002,11030.0 s
Sustained decode02Valid110.655.5431 ms18.0 ms2.003,31730.0 s
Sustained decode04Valid170.440.4673 ms24.7 ms4.005,10730.0 s
Sustained decode08Valid298.837.6731 ms26.6 ms8.008,96330.0 s
Sustained decode016Requests queued305.338.5783 ms26.0 ms8.009,14530.0 s
Sustained decode032Requests queued311.038.6842 ms25.9 ms8.009,32830.0 s
Sustained decode064Requests queued313.038.0959 ms26.3 ms8.009,37930.0 s
Sustained decode0128Requests queued293.438.01,165 ms26.3 ms8.008,80030.0 s
Sustained decode16K1Valid66.866.8736 ms15.0 ms1.002,00430.0 s
Sustained decode16K2Valid119.459.01,156 ms17.0 ms2.003,58130.0 s
Sustained decode16K4Valid153.438.41,632 ms26.1 ms4.004,60130.0 s
Sustained decode16K8Valid287.834.82,781 ms28.7 ms8.008,63130.0 s
Sustained decode16K16Requests queued286.235.82,784 ms28.0 ms8.008,58030.0 s
Sustained decode16K32Requests queued282.134.92,927 ms28.7 ms8.008,45930.0 s
Sustained decode16K64Over capacity————————
Sustained decode16K128Over capacity————————
Sustained decode32K1Valid64.566.0726 ms15.2 ms1.001,93330.0 s
Sustained decode32K2Valid120.160.01,099 ms16.7 ms2.003,60330.0 s
Sustained decode32K4Valid168.142.41,663 ms23.6 ms4.005,04130.0 s
Sustained decode32K8Valid297.137.22,478 ms26.9 ms8.008,90630.0 s
Sustained decode32K16Requests queued296.436.42,627 ms27.5 ms8.008,89330.0 s
Sustained decode32K32Over capacity————————
Sustained decode32K64Over capacity————————
Sustained decode32K128Over capacity————————
Sustained decode64K1Valid70.170.0829 ms14.3 ms1.002,10030.0 s
Sustained decode64K2Valid121.159.11,358 ms16.9 ms2.003,63030.0 s
Sustained decode64K4Valid173.144.52,017 ms22.5 ms4.005,19230.0 s
Sustained decode64K8Valid290.436.02,999 ms27.8 ms8.008,70230.0 s
Sustained decode64K16Over capacity————————
Sustained decode64K32Over capacity————————
Sustained decode64K64Over capacity————————
Sustained decode64K128Over capacity————————
Sustained decode128K1Valid72.173.51,340 ms13.6 ms1.002,16330.0 s
Sustained decode128K2Valid108.554.41,677 ms18.4 ms2.003,25530.0 s
Sustained decode128K4Valid165.440.12,450 ms25.0 ms4.004,96030.0 s
Sustained decode128K8Valid308.437.63,818 ms26.6 ms8.009,24130.0 s
Sustained decode128K16Over capacity————————
Sustained decode128K32Over capacity————————
Sustained decode128K64Over capacity————————
Sustained decode128K128Over capacity————————
Sustained decode248K1Valid82.683.51,997 ms12.0 ms1.002,47430.0 s
Sustained decode248K2Valid105.953.62,975 ms18.7 ms2.003,17530.0 s
Sustained decode248K4Valid176.343.54,370 ms23.0 ms4.005,29030.0 s
Sustained decode248K8Over capacity————————
Sustained decode248K16Over capacity————————
Sustained decode248K32Over capacity————————
Sustained decode248K64Over capacity————————
Sustained decode248K128Over capacity————————

Requests queued: the server could not run all requests at once, so some waited in a queue. Over capacity: not run because this many requests at this context would exceed the server's KV cache.