Divyansh Agrawal (independent) · Released October 19, 2026New
Qwen3.5 4B-Qwenputer has 9.36B parameters. In BF16 its weights alone take 17.4 GiB; quantized to 4-bit, about 6.77 GiB. Each 32K-token request adds 1.00 GiB of KV cache. Cheapest way to run it today: 1 × RTX A4000 (16 GB) at $0.072 per hour. It calls tools and has a thinking mode you can switch off.
Weights plus the KV cache of one request (BF16 cache) and the model's fixed recurrent state, in GiB. Add 1 to 3 GiB for the inference engine itself.
Weights format
Weights only
+ 8K context
+ 32K context
+ 128K context
+ 256K context
BF16 / FP16
17.4
17.7
18.5
21.5
25.5
FP8 / INT8
10.5
10.8
11.6
14.6
18.6
4-bit (GGUF Q4_K_M)
6.77
7.09
7.84
10.8
14.8
How many GPUs to run Qwen3.5 4B-Qwenputer
Fewest GPUs that fit the weights plus one 8K-token request. Data-center GPUs use vLLM (90% of memory usable), the others llama.cpp. Several GPUs split the model with tensor or pipeline parallelism.
GPU
BF16 / FP16
8-bit
4-bit
GeForce RTX 4090 24 GB
1
1
1
GeForce RTX 5090 32 GB
1
1
1
RTX PRO 6000 Blackwell 96 GB
1
1
1
Mac M5 Max 128 GB 96 GB usable
1
1
1
Ryzen AI Max+ 395 128 GB 96 GB usable
1
1
1
DGX Spark (GB10) 128 GB
1
1
1
NVIDIA H100 80 GB
1
1
1
NVIDIA H200 141 GB
1
1
1
NVIDIA B200 (HGX) 180 GB
1
1
1
8-bit: FP8 with vLLM (INT8 on GPUs without FP8), Q8_0 with llama.cpp. 4-bit: AWQ / GPTQ with vLLM, Q4_K_M with llama.cpp, both counted at the Q4_K_M size.
Cheapest way to run Qwen3.5 4B-Qwenputer today
For each GPU: the fewest cards that fit Qwen3.5 4B-Qwenputer with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-11-05).
On-demand prices from AWS, Google Cloud, Azure, RunPod, Vast.ai, Oracle Cloud, OVHcloud, Scaleway, Verda, Akash and UpCloud, checked every hour. Serving many users needs more KV cache, so more memory: size it in the calculator. Some links are affiliate links: StudioTV may earn a commission, at no extra cost to you.
Reasoning. Thinking mode you can switch on or off. With vLLM or SGLang, set it per request: "chat_template_kwargs": {"enable_thinking": false} turns it off, true on. Reasoning tokens take context and KV cache like any other token: leave room for them.
KV cache: how memory grows with context
Architecture: 43 layers · 8 full attention (4 KV × 256) · 35 linear attention. Its KV cache is 5.4× smaller than if every layer used full attention, because only 8 of its 43 layers keep a KV cache; the others hold a small fixed-size state.
Context per request
BF16 cache
FP8 cache
8K tokens
0.25 GiB
0.13 GiB
32K tokens
1.00 GiB
0.50 GiB
128K tokens
4.00 GiB
2.00 GiB
256K tokens
8.00 GiB
4.00 GiB
Plus 71.6 MiB of recurrent state per request, whatever the context.
Qwen3.5 4B-Qwenputer VRAM FAQ
How much VRAM does Qwen3.5 4B-Qwenputer need?
In BF16 the weights alone take 17.4 GiB (19 GB). In FP8 that is 10.5 GiB, and about 6.77 GiB with 4-bit quantization (Q4_K_M). Each request then adds KV cache: 0.25 GiB at 8K tokens and 1.00 GiB at 32K (BF16 cache).
Can Qwen3.5 4B-Qwenputer run on a single RTX 4090 (24 GB)?
Yes. In BF16 it fits on one RTX 4090 with an 8K-token context (17.7 GiB including the cache, with llama.cpp).
Can Qwen3.5 4B-Qwenputer run on an RTX 5090 (32 GB)?
Yes. In BF16 (17.7 GiB with an 8K-token context) it fits on one RTX 5090, with llama.cpp.
Can Qwen3.5 4B-Qwenputer run on a Mac?
Yes. In 4-bit (Q4_K_M with llama.cpp) it needs a Mac with 16 GB of unified memory or more, of which macOS gives the GPU about 11 GB, for one request with an 8K-token context. In 8-bit (Q8_0) it needs 24 GB or more.
Can Qwen3.5 4B-Qwenputer run on a DGX Spark or a Ryzen AI Max+ 395 (128 GB)?
Yes. In BF16 (17.7 GiB with an 8K-token context) it fits on a DGX Spark (128 GB) and on a Ryzen AI Max+ 395 with 128 GB, whose GPU gets up to 96 GB, with llama.cpp and one request.
What is the cheapest way to run Qwen3.5 4B-Qwenputer?
On 2026-11-05, the cheapest on-demand setup is 1 × RTX A4000 (16 GB) with Q8_0 weights on Vast.ai, at $0.072 per hour (about $52.56 per month). Next: 1 × GeForce RTX 3090 (24 GB) with BF16 weights on Vast.ai, at $0.096 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does Qwen3.5 4B-Qwenputer need?
With one request and an 8K-token context: 1 in BF16, 1 in FP8 and 1 in 4-bit (vLLM, 90% of memory usable). Serving many users at once needs more memory for their KV caches: the calculator sizes that for you.
Does Qwen3.5 4B-Qwenputer support tool calling?
Yes, Qwen3.5 4B-Qwenputer supports tool (function) calling: it can ask your application to run a function and use the result.
Does Qwen3.5 4B-Qwenputer have a thinking mode?
Thinking mode you can switch on or off. With vLLM or SGLang, set it per request with "chat_template_kwargs": {"enable_thinking": false} (or true). Reasoning tokens count toward the context and the KV cache.
Qwen3.5 4B-Qwenputer VRAM badge
For a model card or a README: the 4-bit size and the smallest GPU it fits on, linked to this page. Data as JSON: /api/models/qwen3-5-4b-qwenputer.json.
Estimates, not guarantees: computed from the official config.json with the same engine as the LLM VRAM Calculator. Real usage depends on your engine version and settings.