VOOZH about

URL: https://willitrunai.com/can-run/gemma-4-31b-on-m3-ultra-96gb


Can Gemma 4 31B run on Mac Studio M3 Ultra 96GB?

YES — Runs Great

S88Excellent
Estimated from fit model

Gemma 4 31B needs ~44.6 GB VRAM. Mac Studio M3 Ultra 96GB has 69.1 GB. With Q4_K_M quantization, expect ~23 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: HighStack: StandardBottleneck: Balanced
Share:

Operating mode

Choose the run profile you care about

Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.

Current mode

Balanced

Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 44.6 GB, 23.7 tok/s, Runs well
44.6 GB required69.1 GB available
65% VRAM used

Fit status

Runs well

Decode

23.7 tok/s

TTFT

8181 ms

Safe context

43K

Memory

44.6 GB / 69.1 GB

Memory breakdown

Weights18.7 GB
KV Cache14.6 GB
Runtime0.9 GB
Headroom10.4 GB

See how fast it feels

See how fast it feelsGemma 4 31B on Mac Studio M3 Ultra 96GB
1st promptCold start — includes initialization
>Write a Python function to sort a list
Here's a Python function that sorts a list using quicksort: def quicksort(arr): if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) # Example usage numbers = [3, 6, 8, 10, 1, 2, 1] print(quicksort(numbers)) # [1, 1, 2, 3, 6, 8, 10] The algorithm picks a pivot, partitions the list into smaller, equal, and larger elements, then recursively sorts each partition and concatenates the results.
2nd promptWarm — model ready, no init overhead
>Now add type hints and a docstring
def quicksort(arr: list[int]) -> list[int]: """Sort a list using the quicksort algorithm. Args: arr: List of integers to sort. Returns: A new sorted list. """ if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) Added type hints for the input and return type, plus a Google-style docstring.
Estimated: 23.7 tok/s decode · 8.2s TTFT (warm) · 59 tok/s prefill

What limits this setup

This setup is broadly balanced for this model.

Shared-memory contention still exists

The OS, browser, and inference runtime all compete for the same physical memory pool, so real-world headroom is less forgiving than raw capacity suggests.

Best improvement path

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatSRuns well22.5 tok/s4685 ms43K
CodingSRuns well22.5 tok/s8590 ms43K
Agentic CodingSTight fit22.5 tok/s12495 ms43K
ReasoningSRuns well22.5 tok/s10152 ms43K
RAGSTight fit22.5 tok/s15618 ms43K

Quantization options

How Gemma 4 31B (30.700000762939453B params) fits at each quantization level on Mac Studio M3 Ultra 96GB (69.1 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
12.0 GB
LowA78
Q3_K_S
3
15.0 GB
LowA79
NVFP4
4

Get started

Copy-paste commands to run Gemma 4 31B on your machine.

Run

ollama run gemma4:31b

Your hardware

More models your Mac Studio M3 Ultra 96GB can run

ModelParamsGradeDecodeCapabilities
👁 Alibaba
Qwen 3.6 35B A3B
35BS70.8 tok/s
👁 Alibaba

Frequently asked questions

See all results for Mac Studio M3 Ultra 96GBSee all hardware for Gemma 4 31B
17.2 GB
Medium
A79
Q4_K_M
4
18.7 GB
MediumA79
Q5_K_M
5
22.1 GB
HighA80
Q6_K
6
25.2 GB
HighA81
Q8_0Best for your GPU
8
32.8 GB
Very HighA83
F16
16
62.9 GB
MaximumF0
Qwen 3.5 35B A3B
35B
S
77 tok/s
👁 Alibaba
Qwen 3 32B
32BS31 tok/s
👁 Cohere
Command A 111B
111BA6.8 tok/s
👁 Alibaba
Qwen 2.5 VL 72B
72BS13.8 tok/s

Not always. Mac Studio M3 Ultra 96GB can often fit larger models thanks to unified memory, but a discrete GPU with dedicated high-bandwidth VRAM may still decode faster once the model fits. For this combination, the important distinction is capacity versus sustained throughput.