VOOZH about

URL: https://willitrunai.com/can-run/starcoder-15b-on-m4-mini-32gb


Can StarCoder 15B run on Mac mini M4 32GB?

YES — With Q3_K_S

B61Good
Estimated from fit model

StarCoder 15B needs ~26.7 GB VRAM. Mac mini M4 32GB has 23.0 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.

StarCoder 15B at Q5_K_M needs 30.1 GB — too much for Mac mini M4 32GB (23.0 GB). Runs at Q3_K_S (26.7 GB) with low quality. 2 quantization levels fit.
Capabilities:

Select quantization to explore

Q5_K_M (High quality) — 30.1 GB, exceeds 23.0 GB available
30.1 GB required23.0 GB available
131% VRAM needed

7.1 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

5.2 tok/s

TTFT

37407 ms

Safe context

8K

Memory

30.1 GB / 23.0 GB

Offload

20%

Memory breakdown

Weights10.8 GB
KV Cache14.6 GB
Runtime1.2 GB
Headroom3.5 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsStarCoder 15B on Mac mini M4 32GB
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: 5.2 tok/s decode · 37.4s TTFT (warm) · 13 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 1.0 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatARuns with offload8.2 tok/s12941 ms8K
CodingFToo heavy5.6 tok/s34564 ms8K
Agentic CodingFToo heavy3.7 tok/s76688 ms8K
ReasoningFToo heavy5.6 tok/s40849 ms8K
RAGFToo heavy3.7 tok/s95861 ms8K

Quantization options

How StarCoder 15B (15B params) fits at each quantization level on Mac mini M4 32GB (23.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
5.9 GB
LowA71
Q3_K_S
3
7.4 GB
LowA72
NVFP4
4

Get started

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

Run

lms load starcoder && lms server start

Upgrade options

Hardware that runs StarCoder 15B well

Mac mini M4 64GBBudget pick
64 GB Unified (+32)
A
Makes the model fit on the accelerator instead of staying completely out of reach.7.5 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

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

~$1,099 MSRP

MacBook Pro M4 Pro 64GBBest value
64 GB Unified (+32)273 GB/s (+153)
A
Makes the model fit on the accelerator instead of staying completely out of reach.18.3 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

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

~$1,599 MSRP

Mac Studio M2 Ultra 64GBApple upgrade
64 GB Unified (+32)800 GB/s (+680)
A
Makes the model fit on the accelerator instead of staying completely out of reach.43.8 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

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

~$3,999 MSRP

Frequently asked questions

See all results for Mac mini M4 32GBSee all hardware for StarCoder 15B
8.4 GB
Medium
A73
Q4_K_M
4
9.2 GB
MediumA74
Q5_K_M
5
10.8 GB
HighA75
Q6_K
6
12.3 GB
HighA76
Q8_0Best for your GPU
8
16.1 GB
Very HighA75
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.