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.
~$8,000 MSRP
Qwen 3.5 397B A17B needs ~186.2 GB VRAM. Mac Studio M3 Ultra 256GB has 184.3 GB. With Q2_K quantization, expect ~15 tok/s.
Operating mode
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
89.3 GB over capacity — needs offload or smaller quantization
Fit status
Too heavy
Decode
6.9 tok/s
TTFT
28047 ms
Safe context
4K
Memory
273.6 GB / 184.3 GB
Offload
30%
This setup is broadly balanced for this model.
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.
Buy headroom, not only minimum fit
A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | F | Too heavy | 6.9 tok/s | 15207 ms | 4K |
| Coding | F | Too heavy | 6.9 tok/s | 28047 ms | 4K |
| Agentic Coding | F | Too heavy | 6.8 tok/s | 41283 ms | 4K |
| Reasoning | F | Too heavy | 6.9 tok/s | 33147 ms | 4K |
| RAG | F | Too heavy | 6.8 tok/s | 51604 ms | 4K |
How Qwen 3.5 397B A17B (397B params) fits at each quantization level on Mac Studio M3 Ultra 256GB (184.3 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 154.8 GB | Low | F0 |
Q3_K_S | 3 | 194.5 GB | Low | F0 |
NVFP4 | 4 | 222.3 GB | Medium | F0 |
Q4_K_M | 4 | 242.2 GB | Medium | F0 |
Q5_K_M | 5 | 285.8 GB | High | F0 |
Q6_K | 6 | 325.5 GB | High | F0 |
Q8_0 | 8 | 424.8 GB | Very High | F0 |
F16 | 16 | 813.8 GB | Maximum | F0 |
Copy-paste commands to run Qwen 3.5 397B A17B on your machine.
Run
docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
--hf-repo "Qwen/Qwen3.5-397B-A17B-Instruct" \
--hf-file "Qwen3.5-397B-A17B-Instruct-Q4_K_M.gguf" \
-c 4096 -ngl 99升级选项
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.
~$8,000 MSRP
Makes the model fit on the accelerator instead of staying completely out of reach.
Raises estimated decode speed by about 468%.
~$20,000 MSRP
Yes, Mac Studio M3 Ultra 256GB can run Qwen 3.5 397B A17B at Q2_K quantization (Runs with offload (needs ~1.6 GB host RAM)). The recommended Q4_K_M requires 273.6 GB which exceeds available memory, but at Q2_K it needs only 186.2 GB. Expected decode speed: 15.1 tok/s.
Qwen 3.5 397B A17B (397B parameters) requires approximately 273.6 GB at Q4_K_M quantization. On Mac Studio M3 Ultra 256GB, it fits at Q2_K using 186.2 GB.
The recommended quantization is Q4_K_M, but on Mac Studio M3 Ultra 256GB the best fitting quantization is Q2_K, which uses 186.2 GB.
On Mac Studio M3 Ultra 256GB, Qwen 3.5 397B A17B achieves approximately 15.1 tokens per second decode speed with a time-to-first-token of 12815ms using Q2_K quantization.
For coding workloads, Qwen 3.5 397B A17B on Mac Studio M3 Ultra 256GB receives a F grade with 6.9 tok/s and 4K context.
On Mac Studio M3 Ultra 256GB, Qwen 3.5 397B A17B can safely use up to 5K tokens of context at Q2_K quantization. The model's official context limit is 131K, but available memory constrains the safe maximum.
Buy headroom, not only minimum fit. A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.
Not always. Mac Studio M3 Ultra 256GB 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.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/qwen-3.5-397b-a17b-on-m3-ultra-256gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: