# DeepSeek-R1-Distill-Qwen 1.5B on an Apple M3 Ultra (512GB)

Yes — the unquantized weights fit with room for 128k tokens of context.

Canonical page: https://makerportal.ai/lab/llm-vram/deepseek-r1-distill-qwen-1-5b/apple-m3-ultra-512gb
Page title: DeepSeek-R1-Distill-Qwen 1.5B on M3 Ultra 512GB — fits at BF16

This markdown document and the HTML page above are rendered from the same solved values at build time, by the same functions. Nothing here is written by a language model and nothing is fetched at request time.

## Key figures

- **Verdict:** Fits at FP16 — 384.0 GiB usable of 512 GB
- **Usable memory:** 384.0 GiB — 75% of the card's 512 GB — an assumption for unified memory, not a single fraction applied to every device
- **Weights at FP16:** 3.3 GiB — 1.8B parameters
- **Weights (Q4_K_M):** 1.0 GiB — 3.3 GiB at FP16 · 1.8B params · 6 of 6 quant rows are measured files
- **KV cache:** 28.0 KiB per token at FP16 — 28 layers × 2 KV heads × 128 dimensions
- **Speed ceiling:** 216 tok/s — 819 GB/s ÷ bytes read per token
- **Largest context that fits:** 131,072 tokens at FP16 / BF16
- **Trained context:** 131,072 — the cap the KV-cache figures are held to
- **Card bandwidth:** 819 GB/s — 512 GB LPDDR5 unified

## Every quant, against this card

Every quantization of DeepSeek-R1-Distill-Qwen 1.5B against the 384.0 GiB usable on an Apple M3 Ultra (512GB). "Measured" rows are the byte size of a real published file; "nominal" rows are the parameter count times the published bits-per-weight.

| Precision | Bits/weight | Weights | Source | Fits | Max context | Ceiling |
|---|---|---|---|---|---|---|
| FP16 / BF16 | 16.00 | 3.3 GiB | measured file | yes | 131,072 (model cap) | 216 tok/s |
| Q8_0 | 8.53 | 1.8 GiB | measured file | yes | 131,072 (model cap) | 385 tok/s |
| Q6_K | 6.59 | 1.4 GiB | measured file | yes | 131,072 (model cap) | 482 tok/s |
| Q5_K_M | 5.79 | 1.2 GiB | measured file | yes | 131,072 (model cap) | 539 tok/s |
| Q4_K_M | 5.03 | 1.0 GiB | measured file | yes | 131,072 (model cap) | 606 tok/s |
| Q3_K_M | 4.16 | 882 MiB | measured file | yes | 131,072 (model cap) | 706 tok/s |

## Questions this page answers

### How much VRAM does DeepSeek-R1-Distill-Qwen 1.5B need?

3.3 GiB for the weights at FP16 — 1.8B parameters at two bytes each — and 1.0 GiB at Q4_K_M. The KV cache is on top of that and is not a fixed number: this model spends 28.0 KiB per token of context, so 8,192 tokens costs a further 224 MiB. An Apple M3 Ultra (512GB) makes 384.0 GiB of its 512 GB available on the assumption below.

### Can an Apple M3 Ultra (512GB) run DeepSeek-R1-Distill-Qwen 1.5B?

Yes — the unquantized weights fit with room for 128k tokens of context. That is the weights and the KV cache together, against 384.0 GiB of usable memory.

### How fast will DeepSeek-R1-Distill-Qwen 1.5B run on an Apple M3 Ultra (512GB)?

No faster than 216 tokens/second at FP16 / BF16, and in practice below it. Decoding is memory-bound: every token reads all 3.3 GiB of weights plus the cache, and this card moves 819 GB/s. That division is the ceiling — no kernel, runtime or driver beats it, and a real runtime typically reaches 60–80% of it.

### Why does the context length change how much memory DeepSeek-R1-Distill-Qwen 1.5B needs?

Because the KV cache holds one key and one value vector per token, per layer, for the whole conversation, and it is allocated separately from the weights. This model has 28 layers and 2 key/value heads of 128 dimensions, shared across 12 query heads — grouped-query attention, which divides the cache by 6. That works out at 28.0 KiB per token. Parameter count tells you nothing about this number.

## Method and limits

Weight bytes are the byte size of the real published file wherever one exists, and the model's exact parameter count times the published llama.cpp bits-per-weight where it does not. That distinction is on every row above and it matters at both ends: a sub-1B model's Q4_K_M file runs a third larger than the nominal figure because k-quants keep its embedding tables at higher precision, and an already-4-bit release cannot be quantized upward at all. The KV cache is 2 · layers · kv_heads · head_dim · bytes per token, summed over layers with each sliding-window layer capped at its window. The speed figure is a roofline bound, not a benchmark: bandwidth divided by bytes read per token, which no runtime exceeds and every runtime falls short of. The usable fraction of card memory is an assumption: 75% here, which is what this lane assumes for unified memory, where the OS and window server share the same pool — the other class assumes 92%, so it is not one number applied to every device. That is the only assumed input on this page; every other figure is computed from the model config and the card's published specification. Nothing on this page is written by a language model.

## Related tool

[LLM VRAM & KV-Cache Footprint Calculator](https://makerportal.ai/lab/llm-vram-kvcache-calculator) — Interactive VRAM planner — change the model geometry, quantization, context length and card capacity and read the weight bytes, KV-cache bytes and the bandwidth ceiling on decode speed.

---

Source: MakerPortal — https://makerportal.ai/lab/llm-vram/deepseek-r1-distill-qwen-1-5b/apple-m3-ultra-512gb. Free to quote and cite with attribution and a link to the canonical page.