Bắt đầuBảng xếp hạngDecode calculatorMô hìnhOrganizationsReportsMatrix runsPhần cứngĐánh giá chuẩnChợCho thuêProTài liệu API
Ngôn ngữ
Actual Computer — Every computer, one endpoint

Speed test matrix

gemma-4-26B-A4B-it-NVFP4 on CMP 170HX 64GB

vllm · 0.32.0rc1.dev249+g18305948a · NVFP46 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
VRAM
64 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
NVFP4
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: none
# 1x 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 RedHatAI/gemma-4-26B-A4B-it-NVFP4 --max-model-len 262144 --gpu-memory-utilization 0.94 --max-num-seqs 128 --enable-prefix-caching --trust-remote-code --language-model-only

Prefill

prompt tok/s by context length
8K context6,9951,139 ms TTFT
16K context5,7792,729 ms TTFT
32K context4,5006,977 ms TTFT
64K context3,02420,716 ms TTFT
128K context1,83068,396 ms TTFT

Sustained decode

total tok/s · rows are context length, columns are simultaneous requests
Context1248163264128
0149.473 ms TTFT264.4111 ms TTFT444.3107 ms TTFTLooped1,031.8194 ms TTFT1,503.8361 ms TTFT2,071.8551 ms TTFT2,994.2716 ms TTFT
16KLoopedLoopedLoopedLoopedLoopedLooped1,336.24,064 ms TTFTOver capacity
32KLoopedLoopedLoopedLoopedLoopedLoopedOver capacityOver capacity
64KLoopedLoopedLoopedLoopedLoopedOver capacityOver capacityOver capacity
128K73.21,231 ms TTFTLoopedLoopedLoopedOver capacityOver capacityOver capacityOver capacity
248K50.4Requests queued2,439 ms TTFT90.03,427 ms TTFTLoopedOver capacityOver capacityOver capacityOver capacityOver capacity

Requests queued: the server could not run all requests at once, so some waited in a queue. 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
Prefill8K1Valid6,995.0—1,139 ms——1——
Prefill16K1Valid5,779.0—2,729 ms——1——
Prefill32K1Valid4,500.0—6,977 ms——1——
Prefill64K1Valid3,024.0—20,716 ms——1——
Prefill128K1Valid1,830.0—68,396 ms——1——
Sustained decode01Valid149.4151.073 ms6.6 ms1.004,48230.0 s
Sustained decode02Valid264.4133.9111 ms7.5 ms2.007,93630.0 s
Sustained decode04Valid444.3112.9107 ms8.9 ms4.0013,32830.0 s
Sustained decode08Looped—————00—
Sustained decode016Valid1,031.866.9194 ms14.9 ms16.0030,96030.0 s
Sustained decode032Valid1,503.849.6361 ms20.2 ms32.0045,12030.0 s
Sustained decode064Valid2,071.834.3551 ms29.1 ms64.0062,14430.0 s
Sustained decode0128Valid2,994.224.9716 ms40.1 ms128.0089,98430.1 s
Sustained decode16K1Looped—————00—
Sustained decode16K2Looped—————00—
Sustained decode16K4Looped—————00—
Sustained decode16K8Looped—————00—
Sustained decode16K16Looped—————00—
Sustained decode16K32Looped—————00—
Sustained decode16K64Valid1,336.221.24,064 ms47.1 ms64.0040,06430.0 s
Sustained decode16K128Over capacity————————
Sustained decode32K1Looped—————00—
Sustained decode32K2Looped—————00—
Sustained decode32K4Looped—————00—
Sustained decode32K8Looped—————00—
Sustained decode32K16Looped—————00—
Sustained decode32K32Looped—————00—
Sustained decode32K64Over capacity————————
Sustained decode32K128Over capacity————————
Sustained decode64K1Looped—————00—
Sustained decode64K2Looped—————00—
Sustained decode64K4Looped—————00—
Sustained decode64K8Looped—————00—
Sustained decode64K16Looped—————00—
Sustained decode64K32Over capacity————————
Sustained decode64K64Over capacity————————
Sustained decode64K128Over capacity————————
Sustained decode128K1Valid73.273.71,231 ms13.6 ms1.002,19530.0 s
Sustained decode128K2Looped—————00—
Sustained decode128K4Looped—————00—
Sustained decode128K8Looped—————00—
Sustained decode128K16Over capacity————————
Sustained decode128K32Over capacity————————
Sustained decode128K64Over capacity————————
Sustained decode128K128Over capacity————————
Sustained decode248K1Requests queued50.453.82,439 ms18.6 ms0.901,51130.0 s
Sustained decode248K2Valid90.045.63,427 ms21.9 ms2.002,70030.0 s
Sustained decode248K4Looped—————00—
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. 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.