Can InternLM 20B run on MacBook Pro M3 Pro 36GB?

YES — With Q2_K

D38Poor
Estimated from fit model

InternLM 20B needs ~30.9 GB VRAM. MacBook Pro M3 Pro 36GB has 25.9 GB. With Q2_K quantization, expect ~9 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: Very lowStack: StandardBottleneck: Host offload
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.

InternLM 20B at Q5_K_M needs 37.5 GB — too much for MacBook Pro M3 Pro 36GB (25.9 GB). Runs at Q2_K (30.9 GB) with low quality.
Capabilities:

Select quantization to explore

Q5_K_M (High quality) 37.5 GB, exceeds 25.9 GB available
37.5 GB required25.9 GB available
145% VRAM needed

11.6 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

4.7 tok/s

TTFT

40958 ms

Safe context

6K

Memory

37.5 GB / 25.9 GB

Offload

30%

Memory breakdown

Weights14.4 GB
KV Cache18.3 GB
Runtime0.9 GB
Headroom3.9 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsInternLM 20B on MacBook Pro M3 Pro 36GB
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: 4.7 tok/s decode · 41.0s TTFT (warm) · 12 tok/s prefill

What limits this setup

It fits through host-memory offload, and offload is the main reason performance drops.

CPU or host-memory offload is active

About 20% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.

Very little memory headroom

You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.

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

Remove offload with more accelerator memory

Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Buy headroom, not only minimum fit

A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.

Increase host RAM if you keep offloading

This setup may need roughly 1.3 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatCVery compromised (needs ~1.2 GB host RAM)6.7 tok/s15828 ms6K
CodingFToo heavy4.7 tok/s40958 ms6K
Agentic CodingFToo heavy3.5 tok/s80680 ms6K
ReasoningFToo heavy4.7 tok/s48405 ms6K
RAGFToo heavy3.5 tok/s100851 ms6K

Quantization options

How InternLM 20B (20B params) fits at each quantization level on MacBook Pro M3 Pro 36GB (25.9 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
7.8 GB
LowC55
Q3_K_S
3
9.8 GB
LowB56
NVFP4
4
11.2 GB
MediumB57
Q4_K_M
4
12.2 GB
MediumB57
Q5_K_M
5
14.4 GB
HighB58
Q6_KBest for your GPU
6
16.4 GB
HighB58
Q8_0
8
21.4 GB
Very HighF0
F16
16
41.0 GB
MaximumF0

Get started

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

Run

docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \ --hf-repo "internlm/internlm2_5-20b-chat" \ --hf-file "internlm2_5-20b-chat-Q5_K_M.gguf" \ -c 4096 -ngl 99

Upgrade-Optionen

Hardware, die InternLM 20B gut ausführt

Frequently asked questions

Can MacBook Pro M3 Pro 36GB run InternLM 20B?

Yes, MacBook Pro M3 Pro 36GB can run InternLM 20B at Q2_K quantization (Very compromised (needs ~1.3 GB host RAM)). The recommended Q5_K_M requires 37.5 GB which exceeds available memory, but at Q2_K it needs only 30.9 GB. Expected decode speed: 9.2 tok/s.

How much VRAM does InternLM 20B need?

InternLM 20B (20B parameters) requires approximately 37.5 GB at Q5_K_M quantization. On MacBook Pro M3 Pro 36GB, it fits at Q2_K using 30.9 GB.

What is the best quantization for InternLM 20B?

The recommended quantization is Q5_K_M, but on MacBook Pro M3 Pro 36GB the best fitting quantization is Q2_K, which uses 30.9 GB.

What speed will InternLM 20B run at on MacBook Pro M3 Pro 36GB?

On MacBook Pro M3 Pro 36GB, InternLM 20B achieves approximately 9.2 tokens per second decode speed with a time-to-first-token of 21129ms using Q2_K quantization.

Can MacBook Pro M3 Pro 36GB run InternLM 20B for coding?

For coding workloads, InternLM 20B on MacBook Pro M3 Pro 36GB receives a F grade with 4.7 tok/s and 6K context.

What context window can InternLM 20B use on MacBook Pro M3 Pro 36GB?

On MacBook Pro M3 Pro 36GB, InternLM 20B can safely use up to 8K tokens of context at Q2_K quantization. The model's official context limit is 8K, but available memory constrains the safe maximum.

What should I upgrade first if InternLM 20B feels slow on MacBook Pro M3 Pro 36GB?

Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Is unified memory on MacBook Pro M3 Pro 36GB as fast as VRAM for InternLM 20B?

Not always. MacBook Pro M3 Pro 36GB 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 MacBook Pro M3 Pro 36GBSee all hardware for InternLM 20B
Embed this result

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

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

Preview: