llamaperf

Local model performance on your hardware

Find which open-weight LLMs fit in your GPU or Mac and compare the speeds people report on setups like yours.

What runs on your hardware?

Pick your GPU or Mac, then read the speeds people reported on it, or estimate which models fit and how fast they run.

Free to use. No account needed. Memory estimates and community measurements are labelled separately.

Looking for a particular model?

Search for a model to see its reported speeds across GPUs and Macs.

Local model performance reports from the community

These are individual setups, not a controlled benchmark. Compare GPU count, quantization, context and offloading before comparing speeds. How to read a report →

GPU: M5 Ultra 96GB
Compare setup details

Exact recorded values. Context may be a configured limit; matching filters does not establish identical prompts, offloading or concurrency.

Tone: positiveApple hardware
generation:
186.9 tokens/s
quant:
IQ3_S (GGUF)
agentictool-use

User reports Qwen3.8 Flash-Next at 186.9 tok/s on an M5 Ultra Mac Studio with 96GB of RAM under Splash 1.6.1. Setup is Splash with IQ3_S weights, run as a local assistant for editing video in DaVinci Resolve Studio via MCP. The user says the release is a significant improvement in both performance and concurrency, with the peak moving from a width of 4 to a width of 12.

Nov 11, 2026
Apple hardware
generation:
95.0 tokens/s
prompt processing (prefill):
1180.0 tokens/s
quant:
oQ4e

User reports Qwen3.8-27B at about 1180 t/s prompt processing and 95 t/s decode on an M5 Ultra Studio with 96GB of RAM. The model runs with MTP speculation and an oQ4e quant; SSD cache is disabled and the hot cache is set to 4GB with a 10% hit rate. System RAM sits just over 50% during heavy work, and the user asks whether a larger hot cache would be reasonable.

Nov 11, 2026
Tone: mixedApple hardware
generation:
119.0 tokens/s
quant:
6bit
codingagentic

User compares a 6-bit fine-tune of Qwen3.8 27B called sabi-noema against Qwen3.8 Flash-Next on an M5 Ultra Mac Studio 96GB, with MTP enabled for both. The 27B fine-tune reached 119 tok/s against 90 tok/s for Flash-Next, and the user notes better performance on Splash for the 27B. Flash-Next used 2.5x the memory with N-gram offload, 73GB peak versus 29GB peak. The user found the 27B better at coding tests and prose, while Flash-Next did better on broad knowledge.

Nov 7, 2026

Qwen3.8 27B

M5 Ultra 96GB · Ollama · 6,600 ctx

Tone: mixedApple hardware
generation:
52.9 tokens/s
prompt processing (prefill):
1168.0 tokens/s
quant:
MXFP8 (MLX)
kv:
q8_0
codingtool-useagentic

User reports Qwen3.8-27B at 52.9 t/s decode on a 6.6K prompt and 1,168 t/s prompt eval on a Mac Studio M5 Ultra 96GB (64-core GPU), compared against oMLX at 23.3 t/s cold and 29.7 t/s warm on the same model. Setup is Ollama 0.40.13 with the MLX runner, MXFP8 weights, q8_0 KV cache and a 131072 context; the wired memory limit was raised to 86GB. Other Ollama short-prompt speeds: gpt-oss:120b 95 to 102 t/s, qwen3-coder-next 107 t/s, qwen3.6:35b-a3b 246 t/s, llama4:scout 49 t/s. On long prompts gpt-oss prefill was 2,588 t/s at ~15K and 1,996 t/s at ~60K, Coder-Next 3,382 and 2,687 t/s, Qwen3.8 1,376 and 1,243 t/s. The user expected oMLX to win and it did not, and notes Qwen3.8's thinking volume (10,339 tokens, 161 s) as a real cost.

Nov 1, 2026
Tone: positiveApple hardware
generation:
90.0 tokens/s
prompt processing (prefill):
1260.0 tokens/s
quant:
oQ3.5e (MLX)
codingagenticlong-context

User reports Qwen3.8 Flash-Next at 90 tok/s generation and 1,260 tok/s prompt reading on an M5 Ultra Mac Studio with 96 GB, running as a coding agent at 262k context. Setup is oMLX 0.7.2 with the oQ3.5e (~3.5-bit) MLX quant, 60 GB model footprint, 74 GB average and 83 GB peak memory, 2.1 s median time to first token. With Splash as the engine, Flash-Next reached 140 tok/s at Q2_0, 129 tok/s at IQ3_XXS, 132 tok/s at IQ3_S and 79 tok/s at UD-IQ4_XS; Qwen3.8 27B ran at 56 tok/s (oQ8e) and 92 tok/s (UD-Q4_K_M). Two concurrent agents gave 1.52x work per hour at 93 tok/s each, three gave 1.56x at 72 tok/s each. The user notes oMLX crashed out of GPU memory with MTP enabled and multiple agents, and that Flash-Next keeps a ~29 GB lookup table on the SSD.

Oct 29, 2026
Apple hardware
generation:
145.6 tokens/s
prompt processing (prefill):
3880.0 tokens/s
quant:
UD-IQ4_XS (GGUF)
tool-use

User benchmarks Qwen3.8 Flash-Next at 145.6 t/s decode and 3,880 t/s prefill at 1k context on an M5 Ultra 96GB, using Inco Splash 1.5.0 with the UD-IQ4_XS GGUF and an auto-paired DFlash2 drafter. Setup streams weights from disk at about 78 GB resident with 262k context; the 88 GB GGUF sits in the HF cache. Decode falls to 115.4 t/s at 4k and 112.2 t/s at 16k, then reads 163.0 t/s at 32k, 139.8 t/s at 64k and 135.6 t/s at 128k. Figures are medians of 3 reps with unique-nonce prompts and one request in flight; the machine was also serving an agent chat throughout. The post compares Splash against Sushi 2.75bpw, whose numbers are not given here.

Oct 29, 2026
Tone: positiveApple hardware
generation:
144.6 tokens/s
prompt processing (prefill):
3444.0 tokens/s
quant:
IQ3_S (GGUF)
codingagentictool-uselong-context

User reports Qwen3.8 Flash-Next (Swift 1.5) at 144.6 tok/s decode and 3,444 tok/s prefill on a Mac Studio M5 Ultra 96GB, at a median context of 147.5K tokens. Setup is Splash with IQ3_S GGUF weights and a 262,144-token context window, driven by the DeepSeek Harness agent framework for agentic coding. With two concurrent requests combined decode is 200.4 tok/s (100.2 per request) and prefill 3,006 tok/s; with three it is 218.0 tok/s combined (72.7 per request) and 3,253 tok/s prefill, a result the user calls preliminary. The user is happy with the numbers and finds the model less lazy than Sol at troubleshooting.

Oct 26, 2026
Apple hardware
prompt processing (prefill):
1354.0 tokens/s
quant:
iQ-MLX 3.3 bpw (MLX)
codingagenticlong-context

User reports Qwen3.8-Flash-Next on an M5 Ultra 96GB (64-core GPU) prefilling a cold 3.7k-token prompt at 1,354 tok/s. Setup is mlx-serve 26.10.1 with iQ-MLX 3.3 bpw, 131,072 context, native MTP adaptive decoding, PLD and a hot prefix cache, one request at a time. Decode is given per workload only: 227.5 tok/s on copy, 172.8 on new code and 106.4 on novel prose, with speculation on. Cold prefill rose to 4,083 tok/s at 25.2k. An agent replay ran at 125.8 tok/s text-round decode.

Oct 8, 2026

Qwen3.8 27B Swift-1.5

M5 Ultra 96GB · mlx-serve · 25,000 ctx

Tone: positiveApple hardware
generation:
113.7 tokens/s
prompt processing (prefill):
3191.0 tokens/s
quant:
4.7bpw (MLX)

User reports Qwen3.8 Swift-1.5 at 113.7 tok/s decode and 3191 tok/s prefill on an M5 Ultra 96GB Mac Studio. Setup is mlx-serve 26.10.1 with a 4.7bpw MLX quantization, 107GB download, text-only, tested to 179,200 tokens of context. Decode falls to 81.1 tok/s after a 95k prompt, where prefill is 2928 tok/s. User compares against a llama.cpp IQ3_XXS build of the same model, which reaches 62.7 tok/s decode after 4k and 1427 tok/s prefill at 25k. Top-1 agreement with Swift BF16 is 91.0% across 680 held-out positions, against 84.1% for the llama.cpp build.

Oct 6, 2026
Tone: positiveApple hardware
generation:
42.7 tokens/s
prompt processing (prefill):
828.2 tokens/s
quant:
4-bit-8bit mix (MLX)
kv:
8-bit
codingagenticlong-context

User reports Qwen3.8 Flash-Next on a base M5 Ultra 96GB (64-core GPU) at a median 828.2 t/s prefill and 42.7 t/s decode per stream, with a single-stream max of 3,328 t/s prefill and 152 t/s decode. Setup is a custom mlx-serve build with continuous batching at 4-way concurrency, a 4-bit/8-bit mixed MLX quant with MTP, 4 x 128k context (512k total) and 8-bit KV cache using 90GB of unified memory. Aggregate throughput was ~3,200 t/s prefill and ~170.8 t/s decode at 4-way concurrency. The run covered 112M tokens (109M prompt, 3M generated) with an 89% cache hit rate across ~1,700 sub-agent calls.

Sep 23, 2026
Apple hardware
generation:
15.0 tokens/s
quant:
Q8
agentic

User compares an M5 Ultra 96GB against an M5 Max 128GB for running Qwen3.8-27B at Q8, and reports about 15 t/s on the Ultra. The user also discusses Qwen3.8-Flash-Next, a multimodal MoE with 176B total parameters and about 6B active, and estimates it will not fit in 96GB. MLX and llama.cpp are mentioned as possible engines, but the user does not confirm using either.

Sep 7, 2026
Showing 1–11 of 11
Page 1 of 1

Community benchmarks snapshot

Records by GPU

AMD Strix Halo 128GB348NVIDIA RTX 3090271NVIDIA RTX 5090197NVIDIA DGX Spark99NVIDIA RTX 3060 12GB96NVIDIA RTX 5060 Ti 16GB88NVIDIA RTX Pro 6000 Blackwell81AMD Radeon AI PRO R9700 32GB81NVIDIA RTX 5070 Ti77NVIDIA RTX 409068

Records by model

3265 total
Qwen3.81567
Qwen3.6334
Gemma 4185
DeepSeek V4 Flash150
Qwen3.5145
DeepSeek V4.1 Flash103
other781

Records by engine

2307 total
llama.cpp1133
Strata234
vLLM227
MLX107
Ollama99
other507

Use cases

coding 937agentic 640long-context 442tool-use 280vision 173summarization 81math 77creative-writing 58multilingual 35rp 22text-generation 9reasoning 3
coding937agentic640long-context442tool-use280vision173summarization81math77creative-writing58

Median generation t/s by GPU

On Qwen3.8 27B at 4-bit, plain single-GPU runs. Full ranking

RTX 509080RTX Pro 600067RTX 5070 Ti55M5 Ultra 256GB50RTX 409040RX 7900 XTX40RTX 309038RX 7800 XT 16GB35RTX 5090 Laptop 24GB34RX 7900 XT32

Prompt processing, same model

M5 Ultra 256GB1800RTX 40901949RX 7900 XTX640RTX 3090561RX 7900 XT800M3 Ultra 512GB372V100 32GB941Radeon AI PRO R9700 32GB1287RTX 3080 20GB997Arc Pro B70512

Reports by model size

Qwen3.8 27B819Qwen3.8 125B · 6B active676Qwen3.6 35B · 3B active242DeepSeek V4 Flash 284B · 13B active133DeepSeek V4.1 Flash 552B · 16B active92Qwen3.6 27B81Gemma 4 26B · 4B active61GLM-5.3 320B · 18B active57

Quants

Q4_K_M395UD-Q4_K_XL189NVFP4174Q8_01194-bit106IQ4_XS86IQ3_XXS85IQ3_S84Q4_K_XL83Q480