VOOZH about

URL: https://willitrunai.com/can-run/hf-maziyarpanahi--yi-coder-9b-chat-gguf-on-m1-pro-16gb


Can Yi Coder 9B Chat run on MacBook Pro M1 Pro 16GB?

YES — Runs Great

C53Usable
Estimated from fit model

Yi Coder 9B Chat needs ~9.2 GB VRAM. MacBook Pro M1 Pro 16GB has 11.5 GB. With Q4_K_M quantization, expect ~24 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: Very lowStack: StandardBottleneck: Memory bandwidth
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

Q4_K_M (Medium quality) — 9.2 GB, 23.7 tok/s, Runs well
9.2 GB required11.5 GB available
80% VRAM used

Fit status

Runs well

Decode

23.7 tok/s

TTFT

8176 ms

Safe context

52K

Memory

9.2 GB / 11.5 GB

Memory breakdown

Weights5.5 GB
KV Cache1.1 GB
Runtime0.9 GB
Headroom1.7 GB

See how fast it feels

See how fast it feelsYi Coder 9B Chat on MacBook Pro M1 Pro 16GB
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: 23.7 tok/s decode · 8.2s TTFT (warm) · 59 tok/s prefill

What limits this setup

This setup is broadly balanced for this model.

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

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatCRuns well23.7 tok/s4460 ms52K
CodingCRuns well23.7 tok/s8176 ms52K
Agentic CodingCTight fit23.7 tok/s11892 ms52K
ReasoningCRuns well23.7 tok/s9662 ms52K
RAGCTight fit23.7 tok/s14865 ms52K

Quantization options

How Yi Coder 9B Chat (9B params) fits at each quantization level on MacBook Pro M1 Pro 16GB (11.5 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
3.5 GB
LowC50
Q3_K_S
3
4.4 GB
LowC52
NVFP4
4

Get started

Copy-paste commands to run Yi Coder 9B Chat on your machine.

Run

lms load hf-maziyarpanahi--yi-coder-9b-chat-gguf && lms server start

Upgrade options

Hardware that runs Yi Coder 9B Chat well

👁 Intel
Intel Arc B580 12GBBudget pick
456 GB/s (+256)
C
Raises estimated decode speed by about 68%.39.9 tok/s decode

Raises estimated decode speed by about 68%.

~$249 MSRP

👁 NVIDIA
RTX 3060 12GBBest value
360 GB/s (+160)
C
Raises estimated decode speed by about 54%.36.4 tok/s decode

Raises estimated decode speed by about 54%.

~$329 MSRP

Frequently asked questions

See all results for MacBook Pro M1 Pro 16GBSee all hardware for Yi Coder 9B Chat
5.0 GB
Medium
C53
Q4_K_M
4
5.5 GB
MediumC53
Q5_K_M
5
6.5 GB
HighC52
Q6_KBest for your GPU
6
7.4 GB
HighC52
Q8_0
8
9.6 GB
Very HighF0
F16
16
18.5 GB
MaximumF0

Not always. MacBook Pro M1 Pro 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.