willitrun·ai

Can internlm2 5 20b chat run on MacBook Air M2 16GB?

YES — With Q2_K

D35Poor
Estimated from fit model

internlm2 5 20b chat needs ~12.8 GB VRAM. MacBook Air M2 16GB has 11.5 GB. With Q2_K quantization, expect ~6 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.

internlm2 5 20b chat at Q4_K_M needs 17.2 GB — too much for MacBook Air M2 16GB (11.5 GB). Runs at Q2_K (12.8 GB) with low quality.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 17.2 GB, exceeds 11.5 GB available
17.2 GB required11.5 GB available
150% VRAM needed

5.7 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

3.1 tok/s

TTFT

61698 ms

Safe context

4K

Memory

17.2 GB / 11.5 GB

Offload

30%

Memory breakdown

Weights12.2 GB
KV Cache2.3 GB
Runtime0.9 GB
Headroom1.7 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsinternlm2 5 20b chat on MacBook Air M2 16GB
1st promptCold start — includes initialization
>What is local AI inference?
Local AI inference means running an AI language model directly on your own hardware — your laptop, desktop, or server — instead of sending requests to a remote cloud API. When you run inference locally the model weights are loaded into your GPU or unified memory. Each token you generate requires reading those weights from memory, so memory bandwidth is the main bottleneck for decode speed. Key benefits of running locally: - Full privacy: your prompts never leave your machine - No per-token cost or rate limits - Works offline once the model is downloaded - Latency depends only on your hardware
2nd promptWarm — model ready, no init overhead
>How much VRAM do I need?
It depends on the model size and quantization level. A rough rule of thumb: Model size Q4 (4-bit) Q8 (8-bit) FP16 7B params ~4.3 GB ~7.5 GB ~14 GB 13B params ~7.9 GB ~13.9 GB ~26 GB 70B params ~42.7 GB ~74.9 GB ~140 GB Most people use 4-bit quantization (Q4_K_M) which gives 90-95% of full quality at a fraction of the memory. A 24 GB GPU can comfortably run most 7B-13B models.
Estimated: 3.1 tok/s decode · 61.7s TTFT (warm) · 8 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 10% 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 0.8 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatFToo heavy3.4 tok/s31026 ms4K
CodingFToo heavy3.1 tok/s61698 ms4K
Agentic CodingFToo heavy2.7 tok/s103584 ms4K
ReasoningFToo heavy3.1 tok/s72916 ms4K
RAGFToo heavy2.7 tok/s129481 ms4K

Inference speed

internlm2 5 20b chat inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for internlm2 5 20b chat at Q4_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~98 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.

GPU / MacMemoryQuantSpeed (tok/s)Fits?
NVIDIARTX 5090 32GB
32 GBQ4_K_M98.4Fits
NVIDIARTX 4090 24GB
24 GBQ4_K_M62.8Fits
RX 7900 XTX 24GB
24 GBQ4_K_M56.7Fits
NVIDIARTX 3090 24GB
24 GBQ4_K_M53.7Fits
Mac Studio M3 Ultra 256GB
256 GBQ4_K_M45.6Fits
Mac Studio M2 Ultra 128GB
128 GBQ4_K_M38.0Fits
Mac Studio M1 Ultra 128GB
128 GBQ4_K_M36.1Fits
MacBook Pro M4 Max 128GB
128 GBQ4_K_M35.6Fits
MacBook Pro M4 Max 64GB
64 GBQ4_K_M35.6Fits
NVIDIARTX 4080 Super 16GB
16 GBQ4_K_M31.7Heavy offload
MacBook Pro M4 Pro 48GB
48 GBQ4_K_M22.4Fits
MacBook Pro M3 Max 64GB
64 GBQ4_K_M19.7Fits
MacBook Pro M1 Max 64GB
64 GBQ4_K_M18.0Fits
NVIDIARTX 4070 12GB
12 GBQ4_K_M11.2Too big
NVIDIARTX 3060 12GB
12 GBQ4_K_M7.1Too big
NVIDIARTX 4060 8GB
8 GBQ4_K_M2.6Too big

Estimates for single-stream decoding at Q4_K_M; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.

Quantization options

How internlm2 5 20b chat (20B params) fits at each quantization level on MacBook Air M2 16GB (11.5 GB usable).

QuantBitsVRAMQualityFit
Q2_KBest for your GPU
2
7.8 GB
LowC51
Q3_K_S
3
9.8 GB
LowF0
NVFP4
4
11.2 GB
MediumF0
Q4_K_M
4
12.2 GB
MediumF0
Q5_K_M
5
14.4 GB
HighF0
Q6_K
6
16.4 GB
HighF0
Q8_0
8
21.4 GB
Very HighF0
F16
16
41.0 GB
MaximumF0

Get started

Copy-paste commands to run internlm2 5 20b chat on your machine.

Run

lms load hf-bartowski--internlm2-5-20b-chat-gguf && lms server start

升级选项

能流畅运行 internlm2 5 20b chat 的硬件

Frequently asked questions

Can MacBook Air M2 16GB run internlm2 5 20b chat?

Yes, MacBook Air M2 16GB can run internlm2 5 20b chat at Q2_K quantization (Very compromised (needs ~0.8 GB host RAM)). The recommended Q4_K_M requires 17.2 GB which exceeds available memory, but at Q2_K it needs only 12.8 GB. Expected decode speed: 6.0 tok/s.

How much VRAM does internlm2 5 20b chat need?

internlm2 5 20b chat (20B parameters) requires approximately 17.2 GB at Q4_K_M quantization. On MacBook Air M2 16GB, it fits at Q2_K using 12.8 GB.

What is the best quantization for internlm2 5 20b chat?

The recommended quantization is Q4_K_M, but on MacBook Air M2 16GB the best fitting quantization is Q2_K, which uses 12.8 GB.

What speed will internlm2 5 20b chat run at on MacBook Air M2 16GB?

On MacBook Air M2 16GB, internlm2 5 20b chat achieves approximately 6.0 tokens per second decode speed with a time-to-first-token of 32382ms using Q2_K quantization.

Can MacBook Air M2 16GB run internlm2 5 20b chat for coding?

For coding workloads, internlm2 5 20b chat on MacBook Air M2 16GB receives a F grade with 3.1 tok/s and 4K context.

What context window can internlm2 5 20b chat use on MacBook Air M2 16GB?

On MacBook Air M2 16GB, internlm2 5 20b chat can safely use up to 7K tokens of context at Q2_K quantization. The model's official context limit is —, but available memory constrains the safe maximum.

What should I upgrade first if internlm2 5 20b chat feels slow on MacBook Air M2 16GB?

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 Air M2 16GB as fast as VRAM for internlm2 5 20b chat?

Not always. MacBook Air M2 16GB 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 Air M2 16GBSee all hardware for internlm2 5 20b chat
Embed this result

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

<iframe src="https://willitrunai.com/embed/hf-bartowski--internlm2-5-20b-chat-gguf-on-m2-air-16gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: