VOOZH about

URL: https://willitrunai.com/can-run/qwen-3.6-27b-on-m2-24gb


Can Qwen 3.6 27B run on Mac mini M2 24GB?

YES — With NVFP4

A76Great
Estimated from fit model

Qwen 3.6 27B needs ~19.6 GB VRAM. Mac mini M2 24GB has 17.3 GB. With NVFP4 quantization, expect ~3 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.

Qwen 3.6 27B at Q4_K_M needs 23.9 GB — too much for Mac mini M2 24GB (17.3 GB). Runs at NVFP4 (19.6 GB) with medium quality. 3 quantization levels fit.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 20.9 GB, exceeds 17.3 GB available
20.9 GB required17.3 GB available
121% VRAM needed

3.6 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

2.4 tok/s

TTFT

79421 ms

Safe context

4K

Memory

20.9 GB / 17.3 GB

Offload

20%

Memory breakdown

Weights16.5 GB
KV Cache1.0 GB
Runtime0.9 GB
Headroom2.6 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsQwen 3.6 27B on Mac mini M2 24GB
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: 2.4 tok/s decode · 79.4s TTFT (warm) · 6 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.8 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatFToo heavy2.1 tok/s49628 ms4K
CodingFToo heavy2.0 tok/s96800 ms4K
Agentic CodingFToo heavy2.0 tok/s140800 ms4K
ReasoningFToo heavy2.0 tok/s114400 ms4K
RAGFToo heavy2.0 tok/s176000 ms4K

Quantization options

How Qwen 3.6 27B (27B params) fits at each quantization level on Mac mini M2 24GB (17.3 GB usable).

QuantBitsVRAMQualityFit
Q2_KBest for your GPU
2
10.5 GB
LowS93
Q3_K_S
3
13.2 GB
LowF0

Get started

Copy-paste commands to run Qwen 3.6 27B on your machine.

Run

lms load Qwen3.6-27B && lms server start

Upgrade options

Hardware that runs Qwen 3.6 27B well

MacBook Pro M4 32GBBudget pick
32 GB Unified (+8)120 GB/s (+20)
S
Makes the model fit on the accelerator instead of staying completely out of reach.7.1 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.

~$799 MSRP

Mac mini M4 32GBBest value
32 GB Unified (+8)120 GB/s (+20)
S
Makes the model fit on the accelerator instead of staying completely out of reach.7.1 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

Mac mini M4 64GBApple upgrade
64 GB Unified (+40)120 GB/s (+20)
S
Makes the model fit on the accelerator instead of staying completely out of reach.7.1 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

👁 NVIDIA
RTX 5090 32GBBiggest leap
32 GB VRAM (+8)1792 GB/s (+1692)
S
Makes the model fit on the accelerator instead of staying completely out of reach.35.1 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,999 MSRP

Frequently asked questions

See all results for Mac mini M2 24GBSee all hardware for Qwen 3.6 27B
NVFP4
4
15.1 GB
Medium
F0
Q4_K_M
4
16.5 GB
MediumF0
Q5_K_M
5
19.4 GB
HighF0
Q6_K
6
22.1 GB
HighF0
Q8_0
8
28.9 GB
Very HighF0
F16
16
55.4 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.