What GPU do I need to run ccore/Qwen3.5-4B-GLB-3D-Coder?

4.5B parameters, published in F32. View on Hugging Face

4.5B
Parameters
F32
Native precision
Qwen3_5ForConditionalGeneration
Architecture
text-generation
Pipeline

Qwen3.5-4B-GLB-3D-Coder is published by ccore on Hugging Face, with 38,696 downloads and 280 likes to date. It's a Qwen3_5ForConditionalGeneration model built for text-generation, published natively in F32.

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
FP3216.9 GB20.3 GBP401$0.162/hr
cheaper alt.Quadro M40003$0.139/hr
FP8 (quantized)4.2 GB5.1 GBRTX 5060 Ti1$0.180/hr
INT4 (quantized)2.1 GB2.5 GBRTX 30701$0.088/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Cheapest way to run Qwen3.5-4B-GLB-3D-Coder at its published (F32) precision: 1× P40, at $0.162/hr per GPU ($0.162/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

Qwen3.5-4B-GLB-3D-Coder: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Hybrid: only the full-attention layers cache per token; the other layers keep a fixed-size state. Cached per token: 32,768 bytes at 16-bit.

ContextKV cache, one sequence
4K0.13 GB
32K1.0 GB
128K4.0 GB
256K (model maximum)8.0 GB

Computed from the layer, head and window counts in the model's own configuration (ccore/Qwen3.5-4B-GLB-3D-Coder), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

Qwen3.5-4B-GLB-3D-Coder: common questions

Does Qwen3.5-4B-GLB-3D-Coder fit on a 24 GB GPU?

Yes. At FP32 it needs 20.3 GB of VRAM, so a 24 GB card holds it with 3.7 GB to spare. A 16 GB card is not enough for it at FP32.

Can Qwen3.5-4B-GLB-3D-Coder run in 16-bit instead of FP32?

Yes. Its published weights are FP32, 16.9 GB, or 20.3 GB once inference overhead is added. Loading the same weights in 16 bits halves that to 8.5 GB, or 10.1 GB with overhead. That moves it onto a 12 GB card instead of a 24 GB one. How much accuracy the cast costs is model-specific and is not measured here.

What is the least VRAM Qwen3.5-4B-GLB-3D-Coder can run in?

2.5 GB, at INT4 (quantized), which fits a 6 GB card, against 20.3 GB at FP32. That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.

Does quantizing Qwen3.5-4B-GLB-3D-Coder lower the GPU bill?

Yes. At FP32 the cheapest live fit is one P40 at $0.162/hr. At INT4 (quantized) it drops to one RTX 3070 at $0.088/hr, provided a quantized checkpoint exists for it.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More Qwen3.5 models

All 59 Qwen3.5 models: VRAM and GPU requirements

Lineage

Based on Qwen3.5-4B.

Alternatives at this size

Other models for text-generation within about a third of Qwen3.5-4B-GLB-3D-Coder's 4.5B parameters, from other model lines.

More on Qwen3.5-4B-GLB-3D-Coder

Related reading: H100 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, Best GPU for LLM inference, and What AI model fine-tuning is.

Your own GPU cloud accounts

One console for the GPU clouds you already rent from. Your keys stay on your machine.

$20 a month, flat

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.