VOOZH about

URL: https://willitrunai.com/can-run/granite-3.1-8b-on-m1-ultra-64gb


Can Granite 3.1 8B run on Mac Studio M1 Ultra 64GB?

YES — Runs Great

C53Usable
Estimated from fit model

Granite 3.1 8B needs ~14.6 GB VRAM. Mac Studio M1 Ultra 64GB has 46.1 GB. With Q4_K_M quantization, expect ~104 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) — 14.6 GB, 111.5 tok/s, Runs well
14.6 GB required46.1 GB available
32% VRAM used

Fit status

Runs well

Decode

111.5 tok/s

TTFT

1737 ms

Safe context

128K

Memory

14.6 GB / 46.1 GB

Memory breakdown

Weights4.9 GB
KV Cache2.0 GB
Runtime0.9 GB
Headroom6.9 GB

See how fast it feels

See how fast it feelsGranite 3.1 8B on Mac Studio M1 Ultra 64GB
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: 111.5 tok/s decode · 1.7s TTFT (warm) · 279 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
ChatCRuns well103.7 tok/s1018 ms128K
CodingCRuns well103.7 tok/s1867 ms128K
Agentic CodingCRuns well103.7 tok/s2716 ms128K
ReasoningCRuns well103.7 tok/s2207 ms128K
RAGCRuns well103.7 tok/s3395 ms128K

Quantization options

How Granite 3.1 8B (8B params) fits at each quantization level on Mac Studio M1 Ultra 64GB (46.1 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
3.1 GB
LowC46
Q3_K_S
3
3.9 GB
LowC46
NVFP4
4

Get started

Copy-paste commands to run Granite 3.1 8B on your machine.

Run

ollama run granite3.1-dense

Frequently asked questions

See all results for Mac Studio M1 Ultra 64GBSee all hardware for Granite 3.1 8B
4.5 GB
Medium
C46
Q4_K_M
4
4.9 GB
MediumC46
Q5_K_M
5
5.8 GB
HighC47
Q6_K
6
6.6 GB
HighC47
Q8_0
8
8.6 GB
Very HighC47
F16Best for your GPU
16
16.4 GB
MaximumC50

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