# Hy3 on an Apple M4 (24GB)

No. Even Q3_K_M needs 128.1 GiB against 18.0 GiB usable.

Canonical page: https://makerportal.ai/lab/llm-vram/hy3/apple-m4-24gb
Page title: Hy3 VRAM on M4 24GB — does not fit

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:** Does not fit — 18.0 GiB usable of 24 GB
- **Usable memory:** 18.0 GiB — 75% of the card's 24 GB — an assumption for unified memory, not a single fraction applied to every device
- **Weights at FP16:** 556.5 GiB — 298.8B parameters
- **Weights (Q4_K_M):** 169.6 GiB — 556.5 GiB at FP16 · 298.8B params · 6 of 6 quant rows are measured files
- **KV cache:** 320.0 KiB per token at FP16 — 80 layers × 8 KV heads × 128 dimensions
- **Speed ceiling:** 8.0 tok/s — offloaded — nothing fits in device memory
- **Largest context that fits:** none — the weights do not fit
- **Trained context:** 262,144 — the cap the KV-cache figures are held to
- **Card bandwidth:** 120 GB/s — 24 GB LPDDR5X unified

## Every quant, against this card

Every quantization of Hy3 against the 18.0 GiB usable on an Apple M4 (24GB). "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 | 556.5 GiB | measured file | short by 538.5 GiB | — | 2.2 tok/s offloaded |
| Q8_0 | 8.51 | 295.8 GiB | measured file | short by 277.8 GiB | — | 3.9 tok/s offloaded |
| Q6_K | 6.89 | 239.6 GiB | measured file | short by 221.6 GiB | — | 4.7 tok/s offloaded |
| Q5_K_M | 5.70 | 198.2 GiB | measured file | short by 180.2 GiB | — | 5.6 tok/s offloaded |
| Q4_K_M | 4.88 | 169.6 GiB | measured file | short by 151.6 GiB | — | 6.4 tok/s offloaded |
| Q3_K_M | 3.68 | 128.1 GiB | measured file | short by 110.1 GiB | — | 8.0 tok/s offloaded |

## Questions this page answers

### How much VRAM does Hy3 need?

556.5 GiB for the weights at FP16 — 298.8B parameters at two bytes each — and 169.6 GiB at Q4_K_M. The KV cache is on top of that and is not a fixed number: this model spends 320.0 KiB per token of context, so 8,192 tokens costs a further 2.5 GiB. An Apple M4 (24GB) makes 18.0 GiB of its 24 GB available on the assumption below.

### Can an Apple M4 (24GB) run Hy3?

No. Even Q3_K_M needs 128.1 GiB against 18.0 GiB usable. Holding the smallest quant here would need a card with about 171 GB. Splitting the model across the PCIe bus is possible and slow — see the offload figure on this page.

### How fast will Hy3 run on an Apple M4 (24GB)?

It cannot run in this card's memory alone, so the speed is set by whatever bus the offloaded part is read across, not by the 120 GB/s of the card. At an assumed 90 GB/s of host memory bandwidth the ceiling is 8.0 tok/s at Q3_K_M, against 10.4 tok/s if it were resident — 120 GB/s over the 11.56 GB one token reads at Q3_K_M, priced at the 8k reference context. That is the weights the model routes through plus one pass over the cache, against a 137.55 GB weight file.

### Why does the context length change how much memory Hy3 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 80 layers and 8 key/value heads of 128 dimensions, shared across 64 query heads — grouped-query attention, which divides the cache by 8. That works out at 320.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. Because nothing here fits, a second assumed input is in play — the 90 GB/s of host memory bandwidth the offload ceiling is priced at, stated above. Those two are the assumed inputs; 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/hy3/apple-m4-24gb. Free to quote and cite with attribution and a link to the canonical page.