Can Granite Code 20B run on Mac Studio M1 Ultra 128GB?

YES — Runs Great

A75Great

Estimated from fit model

Granite Code 20B needs ~30.1 GB VRAM. Mac Studio M1 Ultra 128GB has 92.2 GB. With Q4_K_M quantization, expect ~36 tok/s.

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

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) — 30.1 GB, 39.0 tok/s, Runs well

30.1 GB required92.2 GB available

33% VRAM used

Fit status

Runs well

Decode

39.0 tok/s

TTFT

4970 ms

Safe context

Memory

30.1 GB / 92.2 GB

Memory breakdown

Weights12.2 GB

KV Cache3.2 GB

Runtime0.9 GB

Headroom13.8 GB

See how fast it feels

See how fast it feelsGranite Code 20B on Mac Studio M1 Ultra 128GB
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: 39.0 tok/s decode · 5.0s TTFT (warm) · 97 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

Workload	Grade	Fit	Decode	TTFT	Context
Chat	A	Runs well	39.0 tok/s	2711 ms	8K
Coding	A	Runs well	36.1 tok/s	5368 ms	8K
Agentic Coding	A	Runs well	39.0 tok/s	7230 ms	8K
Reasoning	A	Runs well	39.0 tok/s	5874 ms	8K
RAG	A	Runs well	39.0 tok/s	9037 ms	8K

Quantization options

How Granite Code 20B (20B params) fits at each quantization level on Mac Studio M1 Ultra 128GB (92.2 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	7.8 GB	Low	B69
Q3_K_S	3	9.8 GB	Low	B69
NVFP4	4	11.2 GB	Medium	B69
Q4_K_M	4	12.2 GB	Medium	B69
Q5_K_M	5	14.4 GB	High	B70
Q6_K	6	16.4 GB	High	B70
Q8_0	8	21.4 GB	Very High	A71
F16Best for your GPU	16	41.0 GB	Maximum	A75

Get started

Copy-paste commands to run Granite Code 20B on your machine.

Run

ollama run granite-code:20b

Your hardware

More models your Mac Studio M1 Ultra 128GB can run

Model	Params	Grade	Decode
Devstral 2 123B Instruct	123B	S	6 tok/s
Qwen3-Coder 30B A3B Instruct	30.5B	S	66.5 tok/s
Qwen 3.5 27B	27B	S	28.9 tok/s
Qwen 3.6 27B	27B	S	21.9 tok/s
Qwen 3.5 122B A10B	122B	S	27.4 tok/s

Frequently asked questions

Can Mac Studio M1 Ultra 128GB run Granite Code 20B?

Yes, Mac Studio M1 Ultra 128GB can run Granite Code 20B with a A grade (Runs well). Expected decode speed: 36.1 tok/s.

How much VRAM does Granite Code 20B need?

Granite Code 20B (20B parameters) requires approximately 30.1 GB of memory with Q4_K_M quantization.

What is the best quantization for Granite Code 20B?

The recommended quantization for Granite Code 20B is Q4_K_M, which balances quality and memory efficiency.

What speed will Granite Code 20B run at on Mac Studio M1 Ultra 128GB?

On Mac Studio M1 Ultra 128GB, Granite Code 20B achieves approximately 36.1 tokens per second decode speed with a time-to-first-token of 5368ms using Q4_K_M quantization.

Can Mac Studio M1 Ultra 128GB run Granite Code 20B for coding?

For coding workloads, Granite Code 20B on Mac Studio M1 Ultra 128GB receives a A grade with 36.1 tok/s and 8K context.

What context window can Granite Code 20B use on Mac Studio M1 Ultra 128GB?

On Mac Studio M1 Ultra 128GB, Granite Code 20B can safely use up to 8K tokens of context. The model's official context limit is 8K, but available memory constrains the safe maximum.

Is unified memory on Mac Studio M1 Ultra 128GB as fast as VRAM for Granite Code 20B?

Not always. Mac Studio M1 Ultra 128GB 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.

See all results for Mac Studio M1 Ultra 128GB See all hardware for Granite Code 20B

Embed this result▼

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/granite-code-20b-on-m1-ultra-128gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: