Can Yi 1.5 34B run on MacBook Pro M3 Max 64GB?

YES — Runs Great

B63Good

○Estimated from fit model

Yi 1.5 34B needs ~32.2 GB VRAM. MacBook Pro M3 Max 64GB has 46.1 GB. With Q4_K_M quantization, expect ~13 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: LowStack: StandardBottleneck: Balanced

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) — 32.2 GB, 12.6 tok/s, Runs well

32.2 GB required46.1 GB available

70% VRAM used

Fit status

Runs well

Decode

12.6 tok/s

TTFT

15409 ms

Safe context

Memory

32.2 GB / 46.1 GB

Memory breakdown

Weights20.7 GB

KV Cache3.7 GB

Runtime0.9 GB

Headroom6.9 GB

See how fast it feels

See how fast it feelsYi 1.5 34B on MacBook Pro M3 Max 64GB
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: 12.6 tok/s decode · 15.4s TTFT (warm) · 31 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

Workload	Grade	Fit	Decode	TTFT	Context
Chat	B	Runs well	12.6 tok/s	8405 ms	4K
Coding	B	Runs well	12.6 tok/s	15409 ms	4K
Agentic Coding	B	Runs well	12.6 tok/s	22414 ms	4K
Reasoning	B	Runs well	12.6 tok/s	18211 ms	4K
RAG	B	Runs well	12.6 tok/s	28017 ms	4K