llamaperf

vLLM benchmarks

An inference server with PagedAttention, built for serving many requests at once.

147 community reports

vLLM results by GPU

Hardware with reported vLLM results, with each report's model, quant and speed, newest first. Runs on several cards, with speculative decoding, with batched requests or with part of the model in system RAM say so, since each describes a different setup.

vLLM on NVIDIA DGX Spark38 reports

All vLLM results on the NVIDIA DGX SparkFilter vLLM reports on the NVIDIA DGX Spark

vLLM on NVIDIA RTX 309025 reports

All vLLM results on the NVIDIA RTX 3090Filter vLLM reports on the NVIDIA RTX 3090

vLLM on NVIDIA CMP 170HX 64GB (unlocked)7 reports

All vLLM results on the NVIDIA CMP 170HX 64GB (unlocked)Filter vLLM reports on the NVIDIA CMP 170HX 64GB (unlocked)

vLLM on AMD Radeon Pro V620 32GB4 reports

Filter vLLM reports on the AMD Radeon Pro V620 32GB

vLLM on Intel Arc Pro B704 reports

Filter vLLM reports on the Intel Arc Pro B70

vLLM on NVIDIA RTX 3080 20GB4 reports

Filter vLLM reports on the NVIDIA RTX 3080 20GB

vLLM on NVIDIA H100 80GB3 reports

Filter vLLM reports on the NVIDIA H100 80GB

vLLM on NVIDIA RTX 5060 Ti 16GB3 reports

Filter vLLM reports on the NVIDIA RTX 5060 Ti 16GB

vLLM, GPU not identified12 reports

vLLM is built for serving many requests together. PagedAttention keeps the KV cache in blocks, the way an operating system pages memory, so many requests can share GPU memory and throughput holds up as requests are added.

llamaperf's medians count one request at a time, which isn't the workload vLLM is designed around. When someone reports batched throughput, the figure stays on their report and never enters a median.

vLLM's GPU backends are CUDA for NVIDIA and ROCm for AMD. It has no Apple Silicon GPU backend of its own.

Compare GPUs running vLLM

Every card is compared on one model, Qwen3.8 27B at 4-bit, the size and bit class that most cards here have plain runs of. A card with no run of that model shows none rather than a figure from a different model.

GPUVRAMReportsMedian speed, Qwen3.8 27B 4-bit
NVIDIA DGX Sparknvidia128GB43no Qwen3.8 27B 4-bit run reported
NVIDIA RTX 3090nvidia24GB30Gen 38.4 t/sPP 561.0 t/s · n=2
NVIDIA RTX Pro 6000 Blackwellnvidia96GB21no Qwen3.8 27B 4-bit run reported
NVIDIA RTX 5090nvidia32GB19Gen 73.2 t/s
AMD Radeon AI PRO R9700 32GBamd32GB16no Qwen3.8 27B 4-bit run reported
NVIDIA CMP 170HX 64GB (unlocked)nvidia64GB7no Qwen3.8 27B 4-bit run reported
AMD Radeon Pro V620 32GBamd32GB6no Qwen3.8 27B 4-bit run reported
Intel Arc Pro B70intel32GB5no Qwen3.8 27B 4-bit run reported

vLLM against other engines

Pairs of plain runs on the same card, of the same model size at the same bit class: one device, one request, no speculative decoding, the whole model in memory. Context length and build still differ between the two sides, and each side shows its own.

Model and GPUvLLMOther engine
Gemma 4 26B · 4B active 4-bitNVIDIA DGX Spark48.2 t/sone generation report, context not statedllama.cpp69.9 t/sPrompt processing (prefill) 2657.0 tokens/s (1)one generation report, 256K context
Qwen3.6 35B · 3B active 16-bitAMD Strix Halo 128GB32.6 t/sPrompt processing (prefill) 3581.0 tokens/s (1)one generation report, 2K contextllama.cpp21.5 t/sPrompt processing (prefill) 484.0 tokens/s (1)one generation report, context not stated
Qwen3.6 35B · 3B active 4-bitNVIDIA DGX Spark78.3 t/sone generation report, 128K contextllama.cpp-Prompt processing (prefill) 3556.7 tokens/s (1)no generation reports, context not stated
Qwen3.8 27B 4-bitNVIDIA RTX 309038.4 t/sPrompt processing (prefill) 561.0 tokens/s (2)one generation report, 144K to 200K contextllama.cpp38.7 t/smedian of 4 generation reports, 128K to 256K context, 1 not stated
Qwen3.8 27B 4-bitNVIDIA RTX 509073.2 t/sone generation report, context not statedllama.cpp84.2 t/smedian of 3 generation reports, 40K to 120K context, 1 not stated
Qwen3-Coder 30B · 3B active 16-bitAMD Instinct MI300X 192GB196.0 t/sone generation report, context not statedSGLang173.0 t/sone generation report, 128K context
Qwen3.8 27B 4-bitNVIDIA RTX 509073.2 t/sone generation report, context not statedTensorSharp80.0 t/sone generation report, 40K context

Top models on vLLM

Frequently asked

Is vLLM faster than other engines?

llamaperf has 6 matched pairs of vLLM and other-engine runs on the same card, model size and bit class, but none is comparable enough to say which engine is faster: the sides have too few reports or were run at different context lengths. A pair counts toward a direction only when each side has at least 3 generation reports with a stated context, and the two sides' contexts overlap. The measured figures and their conditions are in the table on this page.

Does vLLM run on Apple Silicon?

Not on the Mac's GPU. Its GPU backends are CUDA and ROCm. On a Mac, people run llama.cpp's Metal backend or MLX.

What models does vLLM support?

Most open-weight architectures, including Llama, Qwen, Mistral, DeepSeek, Phi and Gemma. It loads AWQ, GPTQ, FP8 and bitsandbytes quants among others.