VOOZH about

URL: https://willitrunai.com/can-run/starcoder2-15b-on-m3-pro-18gb


Can StarCoder2 15B run on MacBook Pro M3 Pro 18GB?

BARELY — Tight on Memory

D38Poor
Estimated from fit model

StarCoder2 15B needs ~14.9 GB VRAM. MacBook Pro M3 Pro 18GB has 13.0 GB. With Q5_K_M quantization, expect ~8 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.

Capabilities:

Select quantization to explore

Q5_K_M (High quality) — 14.9 GB, 9.1 tok/s, Very compromised (needs ~1.4 GB host RAM)
14.9 GB required13.0 GB available
115% VRAM needed

1.9 GB over capacity — needs offload or smaller quantization

Fit status

Very compromised (needs ~1.4 GB host RAM)

Decode

9.1 tok/s

TTFT

21256 ms

Safe context

4K

Memory

14.9 GB / 13.0 GB

Offload

10%

Memory breakdown

Weights10.8 GB
KV Cache1.2 GB
Runtime0.9 GB
Headroom1.9 GB

See how fast it feels

See how fast it feelsStarCoder2 15B on MacBook Pro M3 Pro 18GB
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: 9.1 tok/s decode · 21.3s TTFT (warm) · 23 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 {ram} GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatDVery compromised8.8 tok/s11967 ms4K
CodingDVery compromised8.3 tok/s23205 ms4K
Agentic CodingFToo heavy7.6 tok/s37282 ms4K
ReasoningDVery compromised8.3 tok/s27424 ms4K
RAGFToo heavy7.6 tok/s46603 ms4K

Quantization options

How StarCoder2 15B (15B params) fits at each quantization level on MacBook Pro M3 Pro 18GB (13.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
5.9 GB
LowC54
Q3_K_S
3
7.4 GB
LowC53
NVFP4
4

Get started

Copy-paste commands to run StarCoder2 15B on your machine.

Run

docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \ --hf-repo "bigcode/starcoder2-15b" \ --hf-file "starcoder2-15b-Q5_K_M.gguf" \ -c 4096 -ngl 99

Upgrade options

Hardware that runs StarCoder2 15B well

MacBook Pro M4 32GBBudget pick
32 GB Unified (+14)
C
Removes host-memory offload, which is usually the single biggest latency and throughput win.8.2 tok/s decode

Removes host-memory offload, which is usually the single biggest latency and throughput win.

Adds memory headroom for longer context windows and future model growth.

~$799 MSRP

Mac mini M4 32GBBest value
32 GB Unified (+14)
C
Removes host-memory offload, which is usually the single biggest latency and throughput win.8.2 tok/s decode

Removes host-memory offload, which is usually the single biggest latency and throughput win.

Adds memory headroom for longer context windows and future model growth.

~$1,099 MSRP

MacBook Air M4 24GBApple upgrade
24 GB Unified (+6)
C
Removes host-memory offload, which is usually the single biggest latency and throughput win.8.2 tok/s decode

Removes host-memory offload, which is usually the single biggest latency and throughput win.

Adds memory headroom for longer context windows and future model growth.

~$1,099 MSRP

👁 NVIDIA
RTX 4090 24GBBiggest leap
24 GB VRAM (+6)1008 GB/s (+858)
B
Removes host-memory offload, which is usually the single biggest latency and throughput win.80.8 tok/s decode

Removes host-memory offload, which is usually the single biggest latency and throughput win.

Raises estimated decode speed by about 788%.

~$1,599 MSRP

Frequently asked questions

See all results for MacBook Pro M3 Pro 18GBSee all hardware for StarCoder2 15B
8.4 GB
Medium
C53
Q4_K_MBest for your GPU
4
9.2 GB
MediumC53
Q5_K_M
5
10.8 GB
HighF0
Q6_K
6
12.3 GB
HighF0
Q8_0
8
16.1 GB
Very HighF0
F16
16
30.7 GB
MaximumF0

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.