Get startedLeaderboardDecode calculatorModelsOrganizationsReportsMatrix runsHardwareBenchmarksMarketplaceRentalsProAPI Docs
Language
Actual Computer — Every computer, one endpoint

Speed test matrix

Ornith-1.5-9B-NVFP4 on RTX 3060 12GB

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

Hardware

Type
Discrete GPU
GPU
RTX 3060
VRAM
12 GB
CPU
Intel Xeon E5-2680 v4 (14C)
RAM
32 GB
OS
Ubuntu 24.04.5

Engine

Engine
vllm
Version
0.32.0
Quantization
NVFP4
Backend
cuda
Build
vllm/vllm-openai:v0.32.0-x86_64

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. KV cache: fp8
# 1x RTX 3060 12GB, stock 170 W limit, PCIe Gen3 x16 | Intel Xeon E5-2680 v4 14C | 32 GB DDR4-2400 | Ubuntu 24.04.5, NVIDIA driver 580.178.04
vllm serve ornith-ai/Ornith-1.5-9B-NVFP4 --max-model-len 65536 --gpu-memory-utilization 0.94 --max-num-seqs 73 --enable-prefix-caching --trust-remote-code --language-model-only --kv-cache-dtype fp8

Prefill

prompt tok/s by context length
8K context1,5945,112 ms TTFT
16K context1,50210,735 ms TTFT
32K context1,38223,229 ms TTFT
56K context1,22945,620 ms TTFT

Sustained decode

total tok/s · rows are context length, columns are simultaneous requests
Context1248163264128
053.7104 ms TTFT104.8174 ms TTFT200.5275 ms TTFT367.0498 ms TTFTOver capacityOver capacityOver capacityOver capacity
16K51.5338 ms TTFT98.1469 ms TTFTOver capacityOver capacityOver capacityOver capacityOver capacityOver capacity
32K49.5562 ms TTFT91.9772 ms TTFTOver capacityOver capacityOver capacityOver capacityOver capacityOver capacity
56K46.8405 ms TTFTOver capacityOver capacityOver capacityOver capacityOver capacityOver capacityOver capacity

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
Prefill8K1Valid1,594.0—5,112 ms——1——
Prefill16K1Valid1,502.0—10,735 ms——1——
Prefill32K1Valid1,382.0—23,229 ms——1——
Prefill56K1Valid1,229.0—45,620 ms——1——
Sustained decode01Valid53.753.8104 ms18.6 ms1.001,61130.0 s
Sustained decode02Valid104.852.5174 ms19.0 ms2.003,14530.0 s
Sustained decode04Valid200.550.2275 ms19.9 ms4.006,01530.0 s
Sustained decode08Valid367.046.1498 ms21.7 ms8.0011,01130.0 s
Sustained decode016Over capacity————————
Sustained decode032Over capacity————————
Sustained decode064Over capacity————————
Sustained decode0128Over capacity————————
Sustained decode16K1Valid51.551.6338 ms19.4 ms1.001,54630.0 s
Sustained decode16K2Valid98.148.9469 ms20.4 ms2.002,94230.0 s
Sustained decode16K4Over capacity————————
Sustained decode16K8Over capacity————————
Sustained decode16K16Over capacity————————
Sustained decode16K32Over capacity————————
Sustained decode16K64Over capacity————————
Sustained decode16K128Over capacity————————
Sustained decode32K1Valid49.549.6562 ms20.1 ms1.001,48630.0 s
Sustained decode32K2Valid91.945.8772 ms21.8 ms2.002,75630.0 s
Sustained decode32K4Over capacity————————
Sustained decode32K8Over capacity————————
Sustained decode32K16Over capacity————————
Sustained decode32K32Over capacity————————
Sustained decode32K64Over capacity————————
Sustained decode32K128Over capacity————————
Sustained decode56K1Valid46.846.9405 ms21.3 ms1.001,40530.0 s
Sustained decode56K2Over capacity————————
Sustained decode56K4Over capacity————————
Sustained decode56K8Over capacity————————
Sustained decode56K16Over capacity————————
Sustained decode56K32Over capacity————————
Sustained decode56K64Over capacity————————
Sustained decode56K128Over capacity————————

Over capacity: not run because this many requests at this context would exceed the server's KV cache.