willitrun·ai

Can Cerebras-GPT 13B run on Mac mini M2 24GB?

YES — With Q3_K_S

C52Usable
Estimated from fit model

Cerebras-GPT 13B needs ~19.9 GB VRAM. Mac mini M2 24GB has 17.3 GB. With Q3_K_S quantization, expect ~8 tok/s.

Runtime: OllamaCapacity: OffloadBandwidth: Very lowStack: BasicBottleneck: 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.

Cerebras-GPT 13B at Q5_K_M needs 22.9 GB — too much for Mac mini M2 24GB (17.3 GB). Runs at Q3_K_S (19.9 GB) with low quality. 2 quantization levels fit.
Capabilities:

Select quantization to explore

Q5_K_M (High quality) 22.9 GB, exceeds 17.3 GB available
22.9 GB required17.3 GB available
132% VRAM needed

5.6 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

4.8 tok/s

TTFT

40530 ms

Safe context

7K

Memory

22.9 GB / 17.3 GB

Offload

20%

Memory breakdown

Weights9.4 GB
KV Cache9.8 GB
Runtime1.2 GB
Headroom2.6 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsCerebras-GPT 13B on Mac mini M2 24GB
1st promptCold start — includes initialization
>Solve: If a train travels at 60 mph for 2.5 hours, how far does it go?
Let me work through this step by step. Given information: - Speed = 60 mph (miles per hour) - Time = 2.5 hours Formula: Distance = Speed x Time Calculation: Distance = 60 mph x 2.5 h = 150 miles The train travels 150 miles. Double-check: at 60 mph the train covers 60 miles each hour. In half an hour it covers 30 miles. So in 2.5 hours: 60 + 60 + 30 = 150 miles. Confirmed.
2nd promptWarm — model ready, no init overhead
>What if the train stops for 20 minutes halfway?
The stop doesn't change the total distance covered while moving, but it affects total trip time. Breakdown: - First half: 1.25 hours at 60 mph = 75 miles - Stop: 20 minutes (no distance) - Second half: 1.25 hours at 60 mph = 75 miles Total distance: 150 miles (same) Total time: 2.5 h + 0.33 h = 2.83 hours Average speed: 150 / 2.83 = 53 mph The distance stays the same but average speed drops to 53 mph because of the stop.
Estimated: 4.8 tok/s decode · 40.5s 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 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
ChatBRuns with offload (needs ~0.4 GB host RAM)6.5 tok/s16186 ms7K
CodingFToo heavy4.8 tok/s40530 ms7K
Agentic CodingFToo heavy3.2 tok/s87917 ms7K
ReasoningFToo heavy4.8 tok/s47899 ms7K
RAGFToo heavy3.2 tok/s109896 ms7K

Inference speed

Cerebras-GPT 13B inference speed — tokens per second by GPU & Mac

Estimated decode speed (tokens/sec) for Cerebras-GPT 13B at Q5_K_M across popular GPUs and Apple Silicon, using the fastest local runtime per device. Fastest is RTX 5090 32GB at ~131 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 GBQ5_K_M130.8Fits
NVIDIARTX 4090 24GB
24 GBQ5_K_M83.5Tight
RX 7900 XTX 24GB
24 GBQ5_K_M75.3Tight
NVIDIARTX 3090 24GB
24 GBQ5_K_M71.4Tight
Mac Studio M3 Ultra 256GB
256 GBQ5_K_M60.7Fits
Mac Studio M2 Ultra 128GB
128 GBQ5_K_M50.6Fits
Mac Studio M1 Ultra 128GB
128 GBQ5_K_M47.9Fits
MacBook Pro M4 Max 128GB
128 GBQ5_K_M33.0Fits
MacBook Pro M4 Max 64GB
64 GBQ5_K_M33.0Fits
MacBook Pro M3 Max 64GB
64 GBQ5_K_M26.2Fits
NVIDIARTX 4080 Super 16GB
16 GBQ5_K_M25.7Too big
MacBook Pro M1 Max 64GB
64 GBQ5_K_M24.0Fits
MacBook Pro M4 Pro 48GB
48 GBQ5_K_M20.2Fits
NVIDIARTX 4070 12GB
12 GBQ5_K_M9.0Too big
NVIDIARTX 3060 12GB
12 GBQ5_K_M5.7Too big
NVIDIARTX 4060 8GB
8 GBQ5_K_M3.2Too big

Estimates for single-stream decoding at Q5_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 Cerebras-GPT 13B (13B params) fits at each quantization level on Mac mini M2 24GB (17.3 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
5.1 GB
LowB64
Q3_K_S
3
6.4 GB
LowB65
NVFP4
4
7.3 GB
MediumB66
Q4_K_M
4
7.9 GB
MediumB67
Q5_K_M
5
9.4 GB
HighB67
Q6_KBest for your GPU
6
10.7 GB
HighB67
Q8_0
8
13.9 GB
Very HighF0
F16
16
26.7 GB
MaximumF0

Get started

Copy-paste commands to run Cerebras-GPT 13B on your machine.

Run

docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \ --hf-repo "cerebras/Cerebras-GPT-13B" \ --hf-file "Cerebras-GPT-13B-Q5_K_M.gguf" \ -c 4096 -ngl 99

升级选项

能流畅运行 Cerebras-GPT 13B 的硬件

Frequently asked questions

Can Mac mini M2 24GB run Cerebras-GPT 13B?

Yes, Mac mini M2 24GB can run Cerebras-GPT 13B at Q3_K_S quantization (Very compromised (needs ~0.8 GB host RAM)). The recommended Q5_K_M requires 22.9 GB which exceeds available memory, but at Q3_K_S it needs only 19.9 GB. Expected decode speed: 7.6 tok/s.

How much VRAM does Cerebras-GPT 13B need?

Cerebras-GPT 13B (13B parameters) requires approximately 22.9 GB at Q5_K_M quantization. On Mac mini M2 24GB, it fits at Q3_K_S using 19.9 GB.

What is the best quantization for Cerebras-GPT 13B?

The recommended quantization is Q5_K_M, but on Mac mini M2 24GB the best fitting quantization is Q3_K_S, which uses 19.9 GB.

What speed will Cerebras-GPT 13B run at on Mac mini M2 24GB?

On Mac mini M2 24GB, Cerebras-GPT 13B achieves approximately 7.6 tokens per second decode speed with a time-to-first-token of 25467ms using Q3_K_S quantization.

Can Mac mini M2 24GB run Cerebras-GPT 13B for coding?

For coding workloads, Cerebras-GPT 13B on Mac mini M2 24GB receives a F grade with 4.8 tok/s and 7K context.

What context window can Cerebras-GPT 13B use on Mac mini M2 24GB?

On Mac mini M2 24GB, Cerebras-GPT 13B can safely use up to 12K tokens of context at Q3_K_S quantization. The model's official context limit is 131K, but available memory constrains the safe maximum.

What should I upgrade first if Cerebras-GPT 13B feels slow on Mac mini M2 24GB?

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 Mac mini M2 24GB as fast as VRAM for Cerebras-GPT 13B?

Not always. Mac mini M2 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.

See all results for Mac mini M2 24GBSee all hardware for Cerebras-GPT 13B
Embed this result

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

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

Preview: