llamaperf

What people run, by hardware

Pick the kind of machine you have. You'll see the model sizes people report running on it, most reported first, with the speed they typically get. It tells you what works on hardware like yours. It doesn't tell you which model gives the best answers.

To check a specific model on your exact card, use the calculator. For coding, see the coding models by VRAM.

Maker
NVIDIA
Apple Silicon
Unified-memory PCs
AMD and Intel
No GPU
Model size

Apple Silicon 18-36 GB

Mid-size Macs. Up to about 30B-class models at 4 bits. Memory speed 102 to 461 GB/s across the 18 devices with reports, so a typical figure here spans all of them. 83 single-device reports.

#ModelReports
1Qwen3.827B
Alibaba · mostly 4-bit
Gen 12 t/s (4 runs) · PP 61 t/s (3 runs) · with speculation 27 t/s (7)
17
2Qwen3.635B · 3B active
Alibaba · mostly 4-bit
Gen 40 t/s (5 runs) · PP 355 t/s (2 runs) · with speculation 123 t/s (3)
11
3Qwen3.59B
Alibaba · mostly 4-bit
Gen 49 t/s (2 runs) · with speculation 116 t/s (1)
7
4Qwen3.8 Flash-Next125B · 6B active
Alibaba · mostly Q2_0
No generation data
7
5Gemma 426B · 4B active
Google DeepMind · mostly 4-bit
Gen 52 t/s (1 run)
5
6Gemma 412B
Google DeepMind · mostly Q4_K_M
Gen 13 t/s (1 run) · PP 139 t/s (1 run)
4
7Gemma 4 E4B8B
Google DeepMind · mostly Q4_K_M
No generation data
3
8Ornith1.535B · 3B active
mostly 4-bit
Gen 108 t/s (1 run)
2
9Qwen330B · 3B active
Alibaba · mostly 4-bit
Gen 65 t/s (2 runs) · PP 1063 t/s (1 run)
2
10Qwen38B
Alibaba · mostly Q4_K_M
Gen 22 t/s (2 runs) · PP 224 t/s (1 run)
2
11DeepSeek V4 Flash284B · 13B active
DeepSeek · mostly 2-bit dynamic
No generation data
2
12Gemma 431B
Google DeepMind · mostly Q4_K_M
No generation data
2
13Nemotron 3.5 Lightning30B · 3B active
NVIDIA · mostly Q4_K_M
No generation data
2
14DeepSeek-Coder-V2-Lite16B · 2.4B active
mostly 4bit
Gen 126 t/s (1 run) · PP 364 t/s (1 run)
1
15LFM2.524B · 2.5B active
Liquid AI · mostly Q4_K_M
Gen 52 t/s (1 run)
1
16Llama 3.23B
Meta · mostly Q4_K_M
Gen 46 t/s (1 run) · PP 530 t/s (1 run)
1
17Qwen34B
Alibaba · mostly Q4_K_M
Gen 36 t/s (1 run) · PP 417 t/s (1 run)
1
18Qwen 2.5 Coder7B
mostly Q4_K_M
Gen 23 t/s (1 run) · PP 240 t/s (1 run)
1
19Qwen3.54B
Alibaba · mostly affine Q4, group size 64
Gen 16 t/s (1 run) · PP 439 t/s (1 run)
1
20Qwen314B
Alibaba · mostly 4-bit
Gen 12 t/s (1 run)
1
21Qwen3.8 27B dense27B
Alibaba · mostly 4bit
Gen 9.8 t/s (1 run)
1
22Gemma 327B
Google · mostly 4-bit
Gen 8.9 t/s (1 run) · PP 11 t/s (1 run)
1
23GLM-5.3 Flash320B · 18B active
Zhipu AI · mostly FP8-E4M3
No generation data
1
24Gemma 4 E2B5.1B
Google DeepMind · mostly Q4_K_M
No generation data
1
25Ornith1.5 Ornith1.5-35B-A3B Splash35B · 3B active
No generation data
1
26Qwen30.6B
Alibaba · mostly Q4
No generation data
1
27Qwen3-Next80B · 3B active
Alibaba · mostly Q4_K_M
No generation data
1
28Qwen3.8 Swift-Qwen3.8-27B Splash27B
Alibaba
No generation data
1
29Qwen3.8 Qwen3.8-27B Splash27B
Alibaba
No generation data
1
30gpt-oss21B · 3.6B active
OpenAI
No generation data
1

Not in the table: 15 reports don't say which model size ran. 1 ran on more than one device, which says nothing about what one of them does.

How this list works

Each row is one model size, because a 27B and a 397B from the same family are different choices. Rows are ordered by how many people report running that size on this hardware.

Generation speed is the median of runs on one device, serving one request, without speculative decoding. PP is the median prompt-processing speed from plain runs that reported it, so its run count can be smaller. Speculative decoding (MTP, a draft model, DFlash, n-gram lookup) can make the same model several times faster, so those runs get their own column. A report that doesn't make clear which kind of run it was counts in neither.

Hardware is grouped by how much it holds and how fast its memory is, since memory speed sets how fast a model writes. Click a model for every report behind its row.