# QwQ 32B on a GeForce RTX 4070 Ti SUPER

No. Even Q3_K_M needs 14.9 GiB against 14.7 GiB usable.

Canonical page: https://makerportal.ai/lab/llm-vram/qwq-32b/rtx-4070-ti-super
Page title: QwQ 32B VRAM on RTX 4070 Ti SUPER — 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 — 14.7 GiB usable of 16 GB
- **Usable memory:** 14.7 GiB — 92% of the card's 16 GB — an assumption for a dedicated card, not a single fraction applied to every device
- **Weights at FP16:** 61.0 GiB — 32.8B parameters
- **Weights (Q4_K_M):** 18.4 GiB — 61.0 GiB at FP16 · 32.8B params · 1 of 6 quant rows are measured files
- **KV cache:** 256.0 KiB per token at FP16 — 64 layers × 8 KV heads × 128 dimensions
- **Speed ceiling:** 20.1 tok/s — offloaded — nothing fits in device memory
- **Largest context that fits:** none — the weights do not fit
- **Trained context:** 40,960 — the cap the KV-cache figures are held to
- **Card bandwidth:** 672 GB/s — 16 GB GDDR6X

## Every quant, against this card

Every quantization of QwQ 32B against the 14.7 GiB usable on a GeForce RTX 4070 Ti SUPER. "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 | 61.0 GiB | measured file | short by 46.3 GiB | — | 1.7 tok/s offloaded |
| Q8_0 | 8.50 | 32.4 GiB | nominal | short by 17.7 GiB | — | 3.9 tok/s offloaded |
| Q6_K | 6.56 | 25.0 GiB | nominal | short by 10.3 GiB | — | 5.9 tok/s offloaded |
| Q5_K_M | 5.67 | 21.6 GiB | nominal | short by 6.9 GiB | — | 7.7 tok/s offloaded |
| Q4_K_M | 4.83 | 18.4 GiB | nominal | short by 3.7 GiB | — | 10.9 tok/s offloaded |
| Q3_K_M | 3.91 | 14.9 GiB | nominal | short by 198 MiB | — | 20.1 tok/s offloaded |

## Questions this page answers

### How much VRAM does QwQ 32B need?

61.0 GiB for the weights at FP16 — 32.8B parameters at two bytes each — and 18.4 GiB at Q4_K_M. The KV cache is on top of that and is not a fixed number: this model spends 256.0 KiB per token of context, so 8,192 tokens costs a further 2.0 GiB. A GeForce RTX 4070 Ti SUPER makes 14.7 GiB of its 16 GB available on the assumption below.

### Can a GeForce RTX 4070 Ti SUPER run QwQ 32B?

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

### How fast will QwQ 32B run on a GeForce RTX 4070 Ti SUPER?

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 672 GB/s of the card. At an assumed 90 GB/s of host memory bandwidth the ceiling is 20.1 tok/s at Q3_K_M, against 37.0 tok/s if it were resident — 672 GB/s over the 18.16 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 16.01 GB weight file.

### Why does the context length change how much memory QwQ 32B 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 64 layers and 8 key/value heads of 128 dimensions, shared across 40 query heads — grouped-query attention, which divides the cache by 5. That works out at 256.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: 92% here, which is what this lane assumes for a dedicated card — the other class assumes 75%, 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/qwq-32b/rtx-4070-ti-super. Free to quote and cite with attribution and a link to the canonical page.