Qwen3.5 122B-A10B VRAM requirements

Qwen3.5 122B-A10B needs about 78.2 GB of VRAM at Q4_K_M with 8K context, so it needs an 80 GB card such as the A100 80GB or the H100 SXM; a 24 GB card is too small. Qwen3.5 122B-A10B has 125.1B parameters, of which about 10B are used per token; all 256 experts still have to be in memory. With the same 8K context and one request it needs 129 GB at FP8 and 257 GB at FP16/BF16. The published weights take 233 GB (BF16). It does not fit on a 24 GB card at Q4_K_M; the smallest setup here that holds it with an 8K context is the A100 80GB.

78.2 GB at Q4_K_M, 8K context, one request

FP8
129 GB
FP16 / BF16
257 GB
Published weights
233 GB
Smallest setup, Q4_K_M
A100 80GB
Open Qwen3.5 122B-A10B in the calculator

Worked example: Qwen3.5 122B-A10B with 32K tokens

Inputs: Qwen3.5 122B-A10B · Q4_K_M weights · 32,768 tokens of context · one request · FP16 KV cache

Weights (125.1B at Q4_K_M)
70.5 GB
KV cache (24 KB per token)
768 MB
Buffers and runtime (0.5 GB + 10%)
7.62 GB
Total
78.9 GB

The smallest setup here that holds it is the A100 80GB, with about 1.15 GB to spare. Change the inputs in the calculator

What makes Qwen3.5 122B-A10B's memory use different

36 of its 48 layers keep a fixed-size linear-attention state, so the cache grows by 24 KB per token where caching every layer would take 96 KB.

Per token of context it adds 24 KB of FP16 cache; Mistral Medium 3.5 128B (127.7B), the nearest-sized model here with plain full attention, adds 352 KB, so Qwen3.5 122B-A10B needs 7% as much.

As a mixture-of-experts model it reads about 5.63 GB of its 70.5 GB Q4_K_M weights per generated token (8%), so it writes like a much smaller model while needing memory for all of them.

Running Qwen3.5 122B-A10B with experts in system RAM

llama.cpp's --n-cpu-moe N keeps the experts of the first N layers in RAM. For the measured Q4_K_M GGUF with 32K tokens of context, the smallest N that fits each card, and the speed with 89.6 GB/s of system RAM. Plan the offload for another GPU. The VRAM here can sit below the 78.9 GB of the worked example because it counts the file's measured bytes, keeps the input embedding (token_embd) in system RAM as llama.cpp does and adds a flat 1 GB of buffers, where the estimate above adds 0.5 GB plus 10% to the preset's weights.

GPU--n-cpu-moeVRAM usedIn system RAMTokens/s
RTX 5060 Ti 16GB 16 GB 42 15.2 GB 57.8 GB 8–14
RTX 4090 24 GB 36 23.3 GB 49.7 GB 12–20
RTX 5090 32 GB 30 31.5 GB 41.5 GB 15–26

In system RAM counts the offloaded experts plus the input embedding (token_embd), which stays in RAM even with --n-cpu-moe 0.

How much VRAM does Qwen3.5 122B-A10B need?

Qwen3.5 122B-A10B needs 78.2 GB at Q4_K_M, 137 GB at Q8_0 and 257 GB at FP16 with 8,192 tokens of context and one request. Each total below is the weights plus the FP16 KV cache and the runtime overhead (0.5 GB plus 10%), and each row opens the calculator with that setting. What the GGUF names mean.

Fine-tuning Qwen3.5 122B-A10B? Qwen3.5 122B-A10B VRAM for LoRA, QLoRA and full training.

Qwen3.5 122B-A10B GGUF files on Hugging Face

The 8 GGUF files llama.cpp picks for Qwen3.5 122B-A10B with -hf <repo>:<QUANT>, with the bytes the Hugging Face file list reported on 2026-09-29. Each total is that file plus the FP16 KV cache and 0.5 GB + 10%, one request. "vs estimate" compares the file with the bits-per-weight size the table above uses.

QuantFileSizevs estimate 8K32K128K
Q2_K bartowski/Qwen_Qwen3.5-122B-A10B-GGUF 43.2 GB46,391,154,816 bytes −11% 48.2 GB48.9 GB51.3 GB
Q3_K_M unsloth/Qwen3.5-122B-A10B-GGUF3 parts 52.5 GB56,420,881,952 bytes −8% 58.5 GB59.1 GB61.6 GB
IQ4_XS unsloth/Qwen3.5-122B-A10B-GGUF3 parts 56.1 GB60,229,510,656 bytes −11% 62.4 GB63.0 GB65.5 GB
Q4_K_M unsloth/Qwen3.5-122B-A10B-GGUF3 parts 71.3 GB76,536,964,608 bytes +1% 79.1 GB79.7 GB82.2 GB
Q5_K_M unsloth/Qwen3.5-122B-A10B-GGUF3 parts 85.2 GB91,519,219,200 bytes +3% 94.5 GB95.1 GB97.6 GB
Q6_K unsloth/Qwen3.5-122B-A10B-GGUF4 parts 94.1 GB101,009,782,432 bytes −2% 104 GB105 GB107 GB
Q8_0 unsloth/Qwen3.5-122B-A10B-GGUF4 parts 121 GB129,871,935,104 bytes −2% 134 GB134 GB137 GB
BF16 unsloth/Qwen3.5-122B-A10B-GGUF5 parts 228 GB244,314,011,488 bytes −2% 251 GB252 GB254 GB

GB here is GiB (1024³ bytes), as everywhere on this site; Hugging Face shows the Q4_K_M file as 76.5 GB, in 10⁹ bytes.

Which Qwen3.5 122B-A10B GGUF fits a 16, 24, 32, 48 or 80 GB GPU or a Mac

From the file sizes above: the largest file that fits each machine with an 8K context and 0.5 GB left free, the longest context it then has room for, and the longest context for Q4_K_M (71.3 GB). One request, FP16 KV cache. Where nothing fits, the --n-cpu-moe table above keeps experts in system RAM.

HardwareLargest GGUF, 8KIts longest contextQ4_K_M, longest context
RTX 5060 Ti 16GB None fits — No
RTX 4090 (24 GB) None fits — No
RTX 5090 (32 GB) None fits — No
L40S (48 GB) None fits — No
H100 SXM (80 GB) Q4_K_M, 71.3 GB 22K 22K
M4 Pro Mac (64 GB, 48 GB usable) None fits — No
M4 Max Mac (128 GB, 96 GB usable) Q5_K_M, 85.2 GB 48K 256K (full)

Run Qwen3.5 122B-A10B with llama.cpp or Ollama

llama-server -hf unsloth/Qwen3.5-122B-A10B-GGUF:Q4_K_M -c 32768 --n-cpu-moe 36

Q4_K_M/Qwen3.5-122B-A10B-Q4_K_M-00001-of-00003.gguf, 76.5 GB, from unsloth/Qwen3.5-122B-A10B-GGUF (checked 2026-09-29). On the RTX 4090: 23.3 GB on the card, 49.7 GB in RAM, the --n-cpu-moe 36 row above.

ollama run qwen3.5:122b-a10b

Ollama library tag qwen3.5:122b-a10b; its quant is Ollama's choice. Same context: /set parameter num_ctx 32768.

Qwen3.5 122B-A10B at 8K, 32K, 128K and 256K (full) tokens of context

12 of its 48 layers use full attention and 36 are linear-attention layers with no growing cache. Each extra token of context adds 24 KB of FP16 cache per request. The last column is the smallest setup here, one card or a group, that holds it at Q4_K_M. How the KV cache works.

ContextKV cache, FP16Total at Q4_K_MTotal at Q8_0Smallest setup, Q4_K_M
8K tokens 192 MB 78.2 GB 137 GB A100 80GB
32K tokens 768 MB 78.9 GB 137 GB A100 80GB
128K tokens 3.00 GB 81.3 GB 140 GB Ryzen AI Max+ 395 (128 GB, 96 GB usable)
256K tokens 6.00 GB 84.6 GB 143 GB Ryzen AI Max+ 395 (128 GB, 96 GB usable)

How fast Qwen3.5 122B-A10B writes

Tokens per second for one request with 8,192 tokens of context, estimated from memory bandwidth and the parameters read per token. A dash means it does not fit on one card. Try other settings in the speed calculator.

HardwareBandwidthQ4_K_MFP8
RTX 3060 12GB 360 GB/s ——
RTX 4090 1,008 GB/s ——
RTX 5090 1,792 GB/s ——
M4 Max Mac (128 GB) 546 GB/s 25–43—
M3 Ultra Mac Studio (512 GB) 819 GB/s 37–6323–39
H100 SXM 3,350 GB/s 130–236—
H200 4,800 GB/s 171–322116–211

Longest context on one GPU

How many tokens of context Qwen3.5 122B-A10B fits on a single card with one request, an FP16 KV cache and 0.5 GB left free. "Full" means the model's whole context window fits.

GPUMemoryQ4_K_MQ8_0FP8
RTX 3060 12 GB NoNoNo
RTX 4060 Ti 16GB 16 GB NoNoNo
RTX 3090 / 4090 24 GB NoNoNo
RTX 5090 32 GB NoNoNo
A100 40GB 40 GB NoNoNo
Mac, 64 GB unified memory 48 GB NoNoNo
L40S / RTX 6000 Ada 48 GB NoNoNo
A100 / H100 80GB 80 GB 57KNoNo
Mac, 128 GB unified memory 96 GB 256K (full)NoNo
H200 141 GB 256K (full)148K256K (full)
B200 180 GB 256K (full)256K (full)256K (full)

Model details

Parameters
125.1B (125,086,497,008)
Experts
256 routed experts, all loaded
Active per token
10B
Layers
12 of its 48 layers use full attention and 36 are linear-attention layers with no growing cache
Attention cache
2 KV heads × 256
Context length
262,144 tokens
Published weights
233 GB (BF16)
On Hugging Face
Qwen/Qwen3.5-122B-A10B
Reported benchmarks
GPQA Diamond 86.6 · MMLU-Pro 86.7 · LiveCodeBench v6 78.9. Vendor-reported: from the maker’s own model card, not rerun here; read 2026-09-30.

Why this estimate looks this way

At Q4_K_M and an 8K-token context, Qwen3.5 122B-A10B uses 70.5 GB for weights, 192 MB for its FP16 KV cache and 7.57 GB for estimated runtime overhead, totaling 78.2 GB. The overhead is a 0.5 GB base plus 10% of weights and cache.

This is a mixture-of-experts model: all 256 experts contribute to the 125.1B parameters held in memory, even though only about 10B parameters run per token. Using only active parameters would understate VRAM.

Its attention layout matters for long context: 12 of its 48 layers use full attention and 36 are linear-attention layers with no growing cache. The FP16 cache grows by about 24 KB per additional token per request.

The architecture and published checkpoint size come from the model's config.json and weight files. These are estimates rather than measured peak memory; inference engines can reserve extra buffers or preallocate the full configured cache.

Qwen3.5 122B-A10B next to similar-sized models

The three models here closest to it in parameter count, at Q4_K_M with 8,192 tokens of context.

ModelParametersTotalKV per tokenSmallest setup
Qwen3.5 122B-A10B 125.1B, 10B active 78.2 GB 24 KB A100 80GB
Nemotron 3.5 Super VL 120B-A12B 124.5B, 12B active 77.7 GB 8 KB A100 80GB
Nemotron 3 Super 120B-A12B 123.6B, 12B active 77.2 GB 8 KB A100 80GB
Mistral Medium 3.5 128B 127.7B 82.7 GB 352 KB Ryzen AI Max+ 395 (128 GB, 96 GB usable)

Qwen3.5 122B-A10B VRAM questions

How much VRAM do I need to run Qwen3.5 122B-A10B locally?

About 78.2 GB at Q4_K_M with an 8K context and one request, by the bits-per-weight estimate, and 257 GB at BF16. The Q4_K_M GGUF Q4_K_M/Qwen3.5-122B-A10B-Q4_K_M-00001-of-00003.gguf in unsloth/Qwen3.5-122B-A10B-GGUF is 76,536,964,608 bytes (71.3 GB); with an 8K context it needs 79.1 GB. The smallest setup listed here that holds Q4_K_M is the A100 80GB.

Can I run Qwen3.5 122B-A10B on a 24 GB GPU?

Not entirely in VRAM. The RTX 4090 (24 GB) alone cannot hold it: the smallest listed GGUF, Q2_K at 43.2 GB, needs 48.2 GB with an 8K context. With llama.cpp's --n-cpu-moe 36 and the Q4_K_M GGUF it uses 23.3 GB on the card and 49.7 GB of system RAM at 32K tokens.

Which quantization of Qwen3.5 122B-A10B fits in 16 GB of VRAM?

The RTX 5060 Ti 16GB alone cannot hold it: the smallest listed GGUF, Q2_K at 43.2 GB, needs 48.2 GB with an 8K context. With llama.cpp's --n-cpu-moe 42 and the Q4_K_M GGUF it uses 15.2 GB on the card and 57.8 GB of system RAM at 32K tokens.

Can I run Qwen3.5 122B-A10B on a Mac?

The M4 Pro Mac (64 GB, 48 GB usable) alone cannot hold it: the smallest listed GGUF, Q2_K at 43.2 GB, needs 48.2 GB with an 8K context. On the M4 Max Mac (128 GB, 96 GB usable), the largest listed GGUF that fits with an 8K context and 0.5 GB free is Q5_K_M (85.2 GB), with up to 48K tokens of context. Q4_K_M (71.3 GB) runs with its full 256K-token context. By default macOS lets the GPU use about 75% of unified memory.

How much more VRAM does Qwen3.5 122B-A10B need for 32K or 128K tokens of context?

Its FP16 KV cache is 192 MB at 8K, 768 MB at 32K, 3.00 GB at 128K for one request, so 128K adds 2.81 GB over 8K, plus 10% overhead. A q8_0 cache (-ctk q8_0 -ctv q8_0) takes 1.59 GB at 128K. Its 36 linear-attention layers keep a fixed-size state, so only 12 of 48 layers add cache.

Why does Qwen3.5 122B-A10B use more VRAM than its GGUF file size?

The file holds only the weights. At Q4_K_M with an 8K context: 71.3 GB of weights (the file's 76,536,964,608 bytes) + 192 MB of FP16 KV cache + 7.65 GB of compute buffers and runtime (0.5 GB + 10%) = 79.1 GB.

Does Qwen3.5 122B-A10B need less VRAM because only 10B parameters are active?

No. All 256 experts stay loaded, so the Q4_K_M file takes 71.3 GB. The active parameters decide speed: each generated token reads about 5.63 GB of them. With llama.cpp's --n-cpu-moe 36 and the Q4_K_M GGUF it uses 23.3 GB on the card and 49.7 GB of system RAM at 32K tokens.

Badge for your model card

Paste it into a Hugging Face or GitHub README; it shows the Q4_K_M total above and links to this page. Q8_0 and FP16 badges.

Qwen3.5 122B-A10B VRAM: 78.2 GB at Q4_K_M, 8K context

Numbers read from the model files on Hugging Face on . Compare it with other models in the reproducible model and GPU report.