VOOZH about

URL: https://willitrunai.com/can-run/granite-3.1-8b-on-m4-pro-24gb


Can Granite 3.1 8B run on MacBook Pro M4 Pro 24GB?

YES — Runs Great

B57Good
Estimated from fit model

Granite 3.1 8B needs ~10.3 GB VRAM. MacBook Pro M4 Pro 24GB has 17.3 GB. With Q4_K_M quantization, expect ~50 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: LowStack: 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) — 10.3 GB, 53.3 tok/s, Runs well
10.3 GB required17.3 GB available
60% VRAM used

Fit status

Runs well

Decode

53.3 tok/s

TTFT

3636 ms

Safe context

73K

Memory

10.3 GB / 17.3 GB

Memory breakdown

Weights4.9 GB
KV Cache2.0 GB
Runtime0.9 GB
Headroom2.6 GB

See how fast it feels

See how fast it feelsGranite 3.1 8B on MacBook Pro M4 Pro 24GB
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: 53.3 tok/s decode · 3.6s TTFT (warm) · 133 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
ChatBRuns well53.3 tok/s1983 ms73K
CodingBRuns well49.5 tok/s3908 ms73K
Agentic CodingBRuns well53.3 tok/s5288 ms73K
ReasoningBRuns well53.3 tok/s4297 ms73K
RAGBRuns well53.3 tok/s6610 ms73K

Quantization options

How Granite 3.1 8B (8B params) fits at each quantization level on MacBook Pro M4 Pro 24GB (17.3 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
3.1 GB
LowC51
Q3_K_S
3
3.9 GB
LowC52
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 MacBook Pro M4 Pro 24GBSee all hardware for Granite 3.1 8B
4.5 GB
Medium
C52
Q4_K_M
4
4.9 GB
MediumC53
Q5_K_M
5
5.8 GB
HighC53
Q6_K
6
6.6 GB
HighC54
Q8_0Best for your GPU
8
8.6 GB
Very HighB56
F16
16
16.4 GB
MaximumF0

Not always. MacBook Pro M4 Pro 24GB 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.