What GPU do I need to run Qwen/Qwen-AgentWorld-35B-A3B?

34.7B parameters, published in BF16. View on Hugging Face

34.7B
Parameters
BF16
Native precision
Qwen3_5MoeForConditionalGeneration
Architecture
text-generation
Pipeline

Qwen-AgentWorld-35B-A3B is published by Qwen on Hugging Face, with 71,245 downloads and 710 likes to date. It's a Qwen3_5MoeForConditionalGeneration model built for text-generation, published natively in BF16.

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)
BF1664.6 GB77.5 GBA1001$1.23/hr
cheaper alt.RTX A50004$0.704/hr
FP8 (quantized)32.3 GB38.7 GBRTX 40901$0.558/hr
cheaper alt.RTX 4000 SFF Ada2$0.396/hr
INT4 (quantized)16.1 GB19.4 GBRTX A50001$0.176/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 Qwen-AgentWorld-35B-A3B at its published (BF16) precision: 1× A100, at $1.23/hr per GPU ($1.23/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

Qwen-AgentWorld-35B-A3B: 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: 20,480 bytes at 16-bit.

ContextKV cache, one sequence
4K0.08 GB
32K0.63 GB
128K2.5 GB
256K (model maximum)5.0 GB

Computed from the layer, head and window counts in the model's own configuration (Qwen/Qwen-AgentWorld-35B-A3B), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

Qwen-AgentWorld-35B-A3B: common questions

Can Qwen-AgentWorld-35B-A3B run on a single GPU?

Yes, but not on a desktop card. At BF16 it needs 77.5 GB of VRAM, more than a single 32 GB desktop card holds. The cheapest live single-card fit is a 80.0 GB A100 at $1.23/hr.

What is the least VRAM Qwen-AgentWorld-35B-A3B can run in?

19.4 GB, at INT4 (quantized), which fits a 24 GB card, against 77.5 GB at BF16. 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 Qwen-AgentWorld-35B-A3B lower the GPU bill?

Yes. At BF16 the cheapest live fit is one A100 at $1.23/hr. At INT4 (quantized) it drops to one RTX A5000 at $0.176/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 43 Qwen3.5 models: VRAM and GPU requirements

Lineage

Based on Qwen3.5-35B-A3B-Base.

Alternatives at this size

Other models for text-generation within about a third of Qwen-AgentWorld-35B-A3B's 34.7B parameters, from other model lines.

More on Qwen-AgentWorld-35B-A3B

Related reading: A100 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.

Submit the job. Everything after that is ours.

Sign up in 60 seconds. Pay for the GPU minutes you actually use.

© 2026 Aquanode. All rights reserved.

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