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

Qwen3-0.6B on RTX 3090 24GB

vllm · 0.26.0 · BF164 contexts (0–32K) × 5 concurrency levels (1–16) · prefill at 4K, 16K, 32K
by @Lottolabslmx v0.1.49 runMeasured

Hardware

Type
Discrete GPU
GPU
RTX 3090
VRAM
24 GB
CPU
AMD Ryzen 9 9950X 16-Core Processor
OS
linux

Engine

Engine
vllm
Version
0.26.0
Quantization
BF16

Run

Served model
Qwen/Qwen3-0.6B
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

VLLM_USE_FLASHINFER_SAMPLER=0 vllm serve /home/lotto/models/Qwen3-0.6B --served-model-name Qwen/Qwen3-0.6B --max-model-len 40960 --gpu-memory-utilization 0.9

Prefill

prompt tok/s by context length
4K context30.8K135 ms TTFT
16K context19.2K845 ms TTFT
32K context11.9K2,703 ms TTFT

Sustained decode

total tok/s · rows are context length, columns are simultaneous requests
Context124816
0290.59 ms TTFT422.714 ms TTFT702.613 ms TTFTLooped1,635.728 ms TTFT
4K236.818 ms TTFT358.624 ms TTFTLooped803.651 ms TTFTOver capacity
16K170.546 ms TTFT228.265 ms TTFT316.488 ms TTFTOver capacityOver capacity
32K121.983 ms TTFT150.1112 ms TTFT193.6156 ms TTFTOver 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
Prefill4K1Valid30.8K—135 ms——1——
Prefill16K1Valid19.2K—845 ms——1——
Prefill32K1Valid11.9K—2,703 ms——1——
Sustained decode01Valid290.5316.19 ms3.2 ms1.018,71430.0 s
Sustained decode02Valid422.7223.814 ms4.5 ms2.0012,68030.0 s
Sustained decode04Valid702.6189.613 ms5.3 ms4.0021,07630.0 s
Sustained decode08Looped—————00—
Sustained decode016Valid1,635.7118.528 ms8.4 ms16.0049,05630.0 s
Sustained decode4K1Valid236.8241.118 ms4.1 ms1.007,10330.0 s
Sustained decode4K2Valid358.6184.224 ms5.4 ms2.0010,75830.0 s
Sustained decode4K4Looped—————00—
Sustained decode4K8Valid803.6103.851 ms9.6 ms8.0024,10430.0 s
Sustained decode4K16Over capacity————————
Sustained decode16K1Valid170.5171.746 ms5.8 ms1.005,11330.0 s
Sustained decode16K2Valid228.2115.165 ms8.7 ms2.006,84430.0 s
Sustained decode16K4Valid316.479.888 ms12.5 ms4.009,49230.0 s
Sustained decode16K8Over capacity————————
Sustained decode16K16Over capacity————————
Sustained decode32K1Valid121.9122.383 ms8.2 ms1.003,65830.0 s
Sustained decode32K2Valid150.175.2112 ms13.3 ms2.004,50230.0 s
Sustained decode32K4Valid193.648.5156 ms20.6 ms4.005,80830.0 s
Sustained decode32K8Over capacity————————
Sustained decode32K16Over 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.