Pierwsze krokiRankingDecode calculatorModeleOrganizationsReportsMatrix runsSprzętBenchmarkiMarketplaceWynajemProDokumentacja API
Język
Actual Computer — Every computer, one endpoint

Speed test matrix

Qwen3.5-122B-A10B-GPTQ-Int4 on CMP 170HX 64GB ×2

vllm · 0.32.0rc1.dev249+g18305948a · GPTQ Int46 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.32.0rc1.dev249+g18305948a
Quantization
GPTQ Int4
Backend
cuda
Build
ghcr.io/morrowmake/vllm-cmp170hx@sha256:5b45c4d6feafefe2eba962375b0a9a0b64fd22b9e05abb4d1966f14a32a2db79

Run

Served model
bench
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

# Untuned out-of-the-box baseline. Spec decode: MTP, 2 tokens lookahead. Layout: PP2 (stock vLLM flag)
# 2x NVIDIA CMP 170HX 64GB (cmpunlocker), 180 W limit, PCIe Gen2 x4 | 2x Intel Xeon E5-2630 v3 | 64 GB DDR4 | Ubuntu 26.04.1, NVIDIA driver 610.57.04 | vLLM: Morrowmake vllm-cmp170hx image
vllm serve Qwen/Qwen3.5-122B-A10B-GPTQ-Int4 --max-model-len 262144 --gpu-memory-utilization 0.94 --max-num-seqs 128 --enable-prefix-caching --trust-remote-code --pipeline-parallel-size 2 --language-model-only --speculative-config {"method":"mtp","num_speculative_tokens":2}

Prefill

prompt tok/s by context length
8K context5,4761,487 ms TTFT
16K context5,5492,904 ms TTFT
32K context5,1926,180 ms TTFT
64K context4,38714,594 ms TTFT
128K context3,26439,179 ms TTFT

Sustained decode

total tok/s · rows are context length, columns are simultaneous requests
Context1248163264128
0116.7137 ms TTFT196.7184 ms TTFT307.9249 ms TTFT464.2362 ms TTFT676.0526 ms TTFT971.9773 ms TTFT1,006.6Requests queued876 ms TTFTOver capacity
16K80.0964 ms TTFT130.51,353 ms TTFT197.02,319 ms TTFT323.53,646 ms TTFT416.16,162 ms TTFT510.511,507 ms TTFTOver capacityOver capacity
32K62.21,122 ms TTFT102.71,569 ms TTFT183.32,800 ms TTFT236.53,885 ms TTFT282.66,348 ms TTFTOver capacityOver capacityOver capacity
64K40.51,699 ms TTFT72.02,285 ms TTFT128.44,024 ms TTFT128.85,766 ms TTFTOver capacityOver capacityOver capacityOver capacity
128K26.23,028 ms TTFT47.03,978 ms TTFT52.66,521 ms TTFTOver capacityOver capacityOver capacityOver capacityOver capacity
248K14.94,758 ms TTFT26.76,508 ms TTFTOver capacityOver 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,476.0—1,487 ms——1——
Prefill16K1Valid5,549.0—2,904 ms——1——
Prefill32K1Valid5,192.0—6,180 ms——1——
Prefill64K1Valid4,387.0—14,594 ms——1——
Prefill128K1Valid3,264.0—39,179 ms——1——
Sustained decode01Valid116.7117.7137 ms8.5 ms1.003,50230.0 s
Sustained decode02Valid196.798.4184 ms10.2 ms2.005,89930.0 s
Sustained decode04Valid307.977.1249 ms13.0 ms4.009,23530.0 s
Sustained decode08Valid464.259.1362 ms16.9 ms8.0013,92730.0 s
Sustained decode016Valid676.043.7526 ms22.9 ms16.0020,28130.0 s
Sustained decode032Valid971.931.6773 ms31.6 ms32.0029,16630.0 s
Sustained decode064Requests queued1,006.623.0876 ms43.5 ms52.5030,19330.0 s
Sustained decode0128Over capacity————————
Sustained decode16K1Valid80.081.0964 ms12.4 ms1.002,39930.0 s
Sustained decode16K2Valid130.565.51,353 ms15.3 ms2.003,91430.0 s
Sustained decode16K4Valid197.048.82,319 ms20.5 ms4.005,90930.0 s
Sustained decode16K8Valid323.538.93,646 ms25.7 ms8.009,70230.0 s
Sustained decode16K16Valid416.123.96,162 ms41.9 ms16.0012,47830.0 s
Sustained decode16K32Valid510.513.411,507 ms74.5 ms32.0015,28129.9 s
Sustained decode16K64Over capacity————————
Sustained decode16K128Over capacity————————
Sustained decode32K1Valid62.263.21,122 ms15.8 ms1.001,86630.0 s
Sustained decode32K2Valid102.751.51,569 ms19.4 ms2.003,07930.0 s
Sustained decode32K4Valid183.345.72,800 ms21.9 ms4.005,50030.0 s
Sustained decode32K8Valid236.529.03,885 ms34.5 ms8.007,08730.0 s
Sustained decode32K16Valid282.616.26,348 ms61.6 ms16.008,47430.0 s
Sustained decode32K32Over capacity————————
Sustained decode32K64Over capacity————————
Sustained decode32K128Over capacity————————
Sustained decode64K1Valid40.541.41,699 ms24.2 ms1.001,21530.0 s
Sustained decode64K2Valid72.035.82,285 ms28.0 ms2.002,15930.0 s
Sustained decode64K4Valid128.432.04,024 ms31.3 ms4.003,84930.0 s
Sustained decode64K8Valid128.815.55,766 ms64.4 ms8.003,86130.0 s
Sustained decode64K16Over capacity————————
Sustained decode64K32Over capacity————————
Sustained decode64K64Over capacity————————
Sustained decode64K128Over capacity————————
Sustained decode128K1Valid26.226.63,028 ms37.6 ms1.0078530.0 s
Sustained decode128K2Valid47.023.43,978 ms42.8 ms2.001,41130.0 s
Sustained decode128K4Valid52.613.06,521 ms77.0 ms4.001,57429.9 s
Sustained decode128K8Over capacity————————
Sustained decode128K16Over capacity————————
Sustained decode128K32Over capacity————————
Sustained decode128K64Over capacity————————
Sustained decode128K128Over capacity————————
Sustained decode248K1Valid14.915.24,758 ms65.7 ms1.0044429.8 s
Sustained decode248K2Valid26.713.26,508 ms75.7 ms2.0080130.0 s
Sustained decode248K4Over capacity————————
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.