1792 GB/s (+1392)
A
Raises estimated decode speed by about 528%.38.3 tok/s decode
Raises estimated decode speed by about 528%.
Moves the workload away from shared memory into dedicated accelerator memory.
~$9,999 MSRP
Can Nemotron 70B run on MacBook Pro M3 Max 128GB?
YES — Runs Great
B70Good
○Estimated from fit model
Nemotron 70B needs ~62.3 GB VRAM. MacBook Pro M3 Max 128GB has 92.2 GB. With Q4_K_M quantization, expect ~6 tok/s.
Runtime: llama.cppCapacity: RoomyBandwidth: 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.
Select quantization to explore
Q4_K_M (Medium quality) — 62.3 GB, 6.1 tok/s, Runs well
62.3 GB required92.2 GB available
68% VRAM used
Fit status
Runs well
Decode
6.1 tok/s
TTFT
31673 ms
Safe context
114K
Memory
62.3 GB / 92.2 GB
Memory breakdown
Weights42.7 GB
KV Cache4.9 GB
Runtime0.9 GB
Headroom13.8 GB
See how fast it feels
See how fast it feelsNemotron 70B on MacBook Pro M3 Max 128GB
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: 6.1 tok/s decode · 31.7s TTFT (warm) · 15 tok/s prefill
What limits this setup
The model fits in shared memory, but shared-memory bandwidth is now the real limiter.
Fit does not mean dedicated-VRAM speed
Unified or shared memory can make a model technically fit, but sustained tokens per second may still trail a discrete high-bandwidth GPU with less total memory.
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
Prioritize bandwidth, not only capacity
If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.
Performance by workload
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | B | Runs well | 6.1 tok/s | 17276 ms | 114K |
| Coding | B | Runs well | 6.1 tok/s | 31673 ms | 114K |
| Agentic Coding | A | Runs well | 6.1 tok/s | 46070 ms | 114K |
| Reasoning | B | Runs well | 6.1 tok/s | 37432 ms | 114K |
| RAG | A | Runs well | 6.1 tok/s | 57588 ms | 114K |
Quantization options
How Nemotron 70B (70B params) fits at each quantization level on MacBook Pro M3 Max 128GB (92.2 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 27.3 GB | Low | B64 |
Q3_K_S | 3 | 34.3 GB | Low | B66 |
NVFP4 | 4 | 39.2 GB | Medium | B67 |
Q4_K_M | 4 | 42.7 GB | Medium | B68 |
Q5_K_M | 5 | 50.4 GB | High | B69 |
Q6_K | 6 | 57.4 GB | High | B69 |
Q8_0Best for your GPU | 8 | 74.9 GB | Very High | B69 |
F16 | 16 | 143.5 GB | Maximum | F0 |
Get started
Copy-paste commands to run Nemotron 70B on your machine.
Run
ollama run nemotronUpgrade options