Per iniziareClassificaDecode calculatorModelliOrganizationsReportsMatrix runsHardwareValutazioni comparativeMarketplaceNoleggiProDocumentazione API
Lingua
Actual Computer — Every computer, one endpoint

Speed test matrix

gemma-4-26B-A4B-it on RTX PRO 6000 Blackwell Server Edition 96GB

vllm · 0.30.1rc1.dev452+g73a583112 · 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
RTX PRO 6000 Blackwell Server Edition
VRAM
96 GB
OS
linux

Engine

Engine
vllm
Version
0.30.1rc1.dev452+g73a583112
Quantization
BF16
Backend
cuda
Build
cuda-13.2
Commit
73a5831127a9

Run

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

env MAX_JOBS=2 FLASHINFER_NVCC_THREADS=1 TORCHINDUCTOR_COMPILE_THREADS=1 "$HOME/env_rtxpro6k-redhatai-vllm-73a5831127a9d2b8/bin/vllm" serve RedHatAI/gemma-4-26B-A4B-it --served-model-name gemma --trust-remote-code --tensor-parallel-size 1 --reasoning-parser gemma4 --enable-auto-tool-choice --tool-call-parser gemma4 --max-model-len 262144 --gpu-memory-utilization 0.82 --host 0.0.0.0 --port 8000 --api-key <redacted> --async-scheduling

Prefill

prompt tok/s by context length
8K context21.5K381 ms TTFT
16K context19.5K833 ms TTFT
32K context14.8K2,182 ms TTFT
64K context9,9316,501 ms TTFT
128K context5,94521,697 ms TTFT
251K context3,36775,074 ms TTFT
256K context3,31077,896 ms TTFT

Sustained decode

total tok/s · rows are context length, columns are simultaneous requests
Context1248163264128
8K121.350 ms TTFTLoopedLooped472.3120 ms TTFTLooped1,064.5307 ms TTFTLoopedOver capacity
16KLoopedLoopedLoopedLoopedLoopedLoopedOver capacityOver capacity
32KLoopedLoopedLoopedLoopedLoopedOver capacityOver capacityOver capacity
64KLoopedLoopedLoopedLoopedOver capacityOver capacityOver capacityOver capacity
128KLooped132.2566 ms TTFTLoopedOver capacityOver capacityOver capacityOver capacityOver capacity
251K58.51,004 ms TTFTLoopedOver capacityOver 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
Prefill8K1Valid21.5K—381 ms——1——
Prefill16K1Valid19.5K—833 ms——1——
Prefill32K1Valid14.8K—2,182 ms——1——
Prefill64K1Valid9,931.0—6,501 ms——1——
Prefill128K1Valid5,945.0—21,697 ms——1——
Prefill251K1Valid3,367.0—75,074 ms——1——
Prefill256K1Valid3,310.0—77,896 ms——1——
Sustained decode8K1Valid121.3121.650 ms8.2 ms1.003,63930.0 s
Sustained decode8K2Looped—————00—
Sustained decode8K4Looped—————00—
Sustained decode8K8Valid472.360.0120 ms16.7 ms8.0014,16730.0 s
Sustained decode8K16Looped—————00—
Sustained decode8K32Valid1,064.534.3307 ms29.2 ms32.0031,93530.0 s
Sustained decode8K64Looped—————00—
Sustained decode8K128Over capacity————————
Sustained decode16K1Looped—————00—
Sustained decode16K2Looped—————00—
Sustained decode16K4Looped—————00—
Sustained decode16K8Looped—————00—
Sustained decode16K16Looped—————00—
Sustained decode16K32Looped—————00—
Sustained decode16K64Over capacity————————
Sustained decode16K128Over capacity————————
Sustained decode32K1Looped—————00—
Sustained decode32K2Looped—————00—
Sustained decode32K4Looped—————00—
Sustained decode32K8Looped—————00—
Sustained decode32K16Looped—————00—
Sustained decode32K32Over capacity————————
Sustained decode32K64Over capacity————————
Sustained decode32K128Over capacity————————
Sustained decode64K1Looped—————00—
Sustained decode64K2Looped—————00—
Sustained decode64K4Looped—————00—
Sustained decode64K8Looped—————00—
Sustained decode64K16Over capacity————————
Sustained decode64K32Over capacity————————
Sustained decode64K64Over capacity————————
Sustained decode64K128Over capacity————————
Sustained decode128K1Looped—————00—
Sustained decode128K2Valid132.266.2566 ms15.1 ms2.003,96530.0 s
Sustained decode128K4Looped—————00—
Sustained decode128K8Over capacity————————
Sustained decode128K16Over capacity————————
Sustained decode128K32Over capacity————————
Sustained decode128K64Over capacity————————
Sustained decode128K128Over capacity————————
Sustained decode251K1Valid58.558.71,004 ms17.0 ms1.001,75630.0 s
Sustained decode251K2Looped—————00—
Sustained decode251K4Over capacity————————
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.