Mac setups
M5 Ultra Mac Studio for local LLMs: early measurements
By llamaperf · · 7 min read
Quick answer
In llama.cpp's standard test the M5 Ultra Mac Studio writes text about 1.6 times as fast as an M5 Max, and it reads prompts far faster than the M3 Ultra it replaces. When a model fits in 32 GB, an RTX 5090 still writes faster. The Ultra is for memory and long prompts, and you should size it against the share of memory macOS lets the GPU use.
What Apple shipped
Memory and bandwidth by configuration
The new Mac Studio went on sale on 22 September with two chips in four configurations. For a local model, look at memory bandwidth before anything else, because writing each token means reading the model's weights out of memory again. These are the figures Apple's tech specs list:
| Chip | GPU cores | Memory | Bandwidth |
|---|---|---|---|
| M5 Max | 32 | 36 GB | 460 GB/s |
| M5 Max | 40 | 48, 64 or 128 GB | 614 GB/s |
| M5 Ultra | 64 | 96 or 256 GB | 1.2 TB/s |
| M5 Ultra | 80 | 256 or 512 GB | 1.2 TB/s |
The 96 GB Ultra is the cut-down 64-core part, which people in threads sometimes mistake for the full chip. The 64-core GPU also supports 256 GB. That memory capacity does not require the 80-core GPU. The 512 GB option requires the 80-core GPU, and Apple says it arrives later than the rest.
What Apple's own claim covers
Apple's launch release makes a single LLM claim:
"Up to 9.8x faster LLM prompt processing in LM Studio when compared to Mac Studio with M1 Ultra, and up to 4x faster than M3 Ultra." (Apple Newsroom, 25 August 2026)
That figure is for prompt processing, where the model reads what you sent. It doesn't cover how fast text comes back, and the release doesn't name a model or a quantization. Read it as the best you'll see on long prompts, and go to owners' numbers for everything else.
What owners measured
The same test on three Macs
The most useful comparison comes from the long-running Apple Silicon thread in llama.cpp. Everyone there runs the same small model through llama-bench with speculation off and posts the result (llama.cpp discussion 4167). These are the rows for its 8-bit version:
| Chip | Reads the prompt (t/s) | Writes text (t/s) |
|---|---|---|
| M5 Ultra, 80 cores | 4,910.55 | 119.01 |
| M5 Max, 40 cores | 3,143.81 | 72.42 |
| M3 Ultra, 80 cores | 1,487.51 | 63.93 |
An owner of a 256 GB Mac Studio posted the M5 Ultra row on 30 September. Nobody had posted the 64-core Ultra or the 32-core Max as of 1 October, so the 96 GB and 36 GB models were still unmeasured.
Qwen on a longer prompt
For a larger workload, MacStories ran Qwen3.8 27B on a 6,091-token prompt with speculation off: the M5 Ultra read it at 1,701 tokens a second and wrote at 48, the M3 Ultra managed 414 and 31, and an RTX 5090 in the same test read at 3,031 and wrote at 59 (MacStories review). Federico Viticci puts the reason plainly:
"Token generation, on the other hand, is bandwidth: the model writes one token at a time and pulls the entire model back out of memory for each one" (MacStories)
The 5090 has 1.79 TB/s to the Ultra's 1.2, which keeps it ahead on writing for any model that fits in its 32 GB. Go bigger than that and the Mac wins by default, since the 5090 has to borrow system memory. The Mac page has reports from people running these machines, each with its model, quant and engine.
Ultra or Max
Twice the bandwidth isn't twice the speed
On paper the Ultra has double the Max's bandwidth, yet in the llama.cpp test it writes 1.64 times as fast (119.01 against 72.42). Every Ultra so far has lost some speed to the link between its two halves, and the M5 Ultra is no exception. If your models fit in 128 GB and you mostly chat, an M5 Max gets you most of the way for less than half the starting price: $2,499 against $5,499 in the US, per Apple's release.
The Ultra pays for itself on long prompts, which it reads much faster, so it suits you if you paste in whole codebases or long documents. It's also the only Mac with more than 128 GB. Before choosing the Ultra, name the model or long-prompt workload that needs its capacity or speed.
The memory a model can use
macOS won't hand the GPU all of your memory. On Macs with 36 GB or more it allows about three quarters by default, which leaves a model about 72 GB on a 96 GB Ultra and about 192 GB on a 256 GB one. MacStories ran into that limit even at 256 GB, where two large Flash-Next builds only fit once parts of them were moved to the SSD. Check your model against the real limit before you choose a memory size. The calculator has a Mac tab where you pick Mac Studio, the chip and the memory, and it grades every model against that share. To raise the limit, see the Apple Silicon section of the VRAM guide.
Read the fastest numbers carefully
Check whether speculation was on
The M5 Ultra figure you'll see quoted most is 108 tokens a second on Qwen3.8 Flash-Next. MacStories got it with multi-token prediction (MTP) at depth 3, where the model drafts several tokens and checks them in one pass. The result is real, and most owners will want MTP on, but compare it only with other MTP runs, because a plain run on another machine measures something else. One owner who tested Flash-Next on a 256 GB M5 Ultra put MTP at "roughly 2x" the plain speed (r/LocalLLaMA). Our speculative decoding guide goes into when that gain holds up.
Builds move results too
In the llama.cpp thread, the M3 Ultra rows came from a 2023 build of llama.cpp and the M5 rows from a 2026 one. The build difference affects that comparison. On an M2 Ultra, the newer build with flash attention on took 8-bit writing speed from 66.64 to 82.83 tokens a second, so part of the M5 Ultra's lead over the M3 Ultra in that table is two years of llama.cpp work. Compare two Macs on the same build where you can, and read a gap between different builds as rough.
Frequently asked questions
Is the M5 Ultra twice as fast as the M5 Max for local LLMs?
No. Its memory bandwidth is double, but in llama.cpp's standard test it writes text about 1.64 times as fast: 119 against 72 tokens a second on an 8-bit model. Where the Ultra pulls well ahead is reading long prompts.
Should I buy the 96 GB M5 Ultra or the 128 GB M5 Max?
It comes down to how big your models are. The 96 GB Ultra has faster memory but the 64-core GPU, and by default a model gets about 72 GB of it. The 128 GB Max gives a model about 96 GB at half the bandwidth. Models that fit in 72 GB run faster on the Ultra. If yours don't, the Max can run them and the Ultra can't.
How much memory can a model use on a 256 GB Mac Studio?
About 192 GB, three quarters of the machine, unless you change it. The iogpu.wired_limit_mb setting raises the limit, and whatever extra you give the GPU comes out of what macOS and your other apps can use.
Is an RTX 5090 faster than the M5 Ultra?
If the model fits in its 32 GB, yes. MacStories measured Qwen3.8 27B writing at 59 tokens a second on a 5090 and 48 on the M5 Ultra. Once a model needs more than 32 GB, the 5090 has to fall back on system memory and slows down sharply, and the Mac keeps going.
Why do some M5 Ultra speeds look so much higher than others?
Speculation, most of the time. Multi-token prediction and draft models can roughly double writing speed, and a lot of headline figures use one or the other. Look for a note that it was a plain run before you hold it up against another machine.
Do I need the 512 GB Mac Studio?
Consider it when the very largest models are part of your workload. The 256 GB model already gives the GPU about 192 GB by default. The 512 GB version also ships later than the others, and one 256 GB owner already finds the GPU slow for that much memory, so doubling the memory gets you room for bigger models at the same writing speed.