On-prem models / Alibaba Qwen

Run Qwen3-30B-A3B-Instruct-2507 on-prem

July 2025 refresh of the Qwen3 30B MoE in non-thinking form, 3.3B active. A very common local model because it is fast on modest GPUs and CPUs.

30.5B MoE (3.3B active)256K contextApache-2.0texttool callingreleased 2025-07

Memory needed

PrecisionWeightsKV per request, 8KKV per request, 32KKV per request, 128K
BF16 (full precision)61.0 GB0.81 GB3.22 GB12.9 GB
FP830.5 GB0.40 GB1.61 GB6.44 GB
INT4 (AWQ / GPTQ)17.1 GB0.40 GB1.61 GB6.44 GB
GGUF Q4_K_M18.3 GB0.40 GB1.61 GB6.44 GB

KV cache from the published config: 48 layers, 4 KV heads x 128 dims. 16-bit cache for BF16 rows, 8-bit otherwise.

Fit for ERP and manufacturing work

Good for cheap, fast assistants over ERP data: summarising orders, drafting supplier emails, simple tool calls. For new builds, Qwen3.6-35B-A3B gives vision and better agents at similar cost.

Strengths

  • Fast decode on consumer and workstation hardware
  • Broad engine support including Ollama and llama.cpp
  • 256K native context
  • Apache 2.0

Watch out for

  • Non-thinking only (a separate Thinking-2507 repo exists)
  • Full attention on all 48 layers, so KV grows faster than in Qwen3.5+ hybrids
  • Largely superseded by Qwen3.6-35B-A3B

GPUs that run it

One user, 8K context, FP8

HardwareCountMemory usedTok/s per user
NVIDIA A100 40GB PCIe133 / 36 GB153
NVIDIA L4 24GB234 / 43 GB59
NVIDIA A10 24GB234 / 43 GB103
NVIDIA L40S 48GB133 / 43 GB95
NVIDIA RTX A6000 48GB133 / 43 GB86
NVIDIA RTX 6000 Ada 48GB133 / 43 GB104
NVIDIA GeForce RTX 4090 24GB234 / 43 GB148
NVIDIA GeForce RTX 5090 32GB234 / 57 GB205

20 people at once, 16K context, FP8

HardwareCountMemory usedTok/s per user
NVIDIA GeForce RTX 5090 32GB250 / 57 GB96
AMD Instinct MI210 64GB149 / 57 GB57
NVIDIA A100 40GB PCIe250 / 72 GB86
NVIDIA A100 80GB PCIe149 / 72 GB67
NVIDIA A100 80GB SXM149 / 72 GB71
NVIDIA H100 PCIe 80GB149 / 72 GB70
NVIDIA H100 SXM 80GB149 / 72 GB109
NVIDIA H100 NVL 94GB149 / 84 GB123

Serving and licence

vllm>=0.8.5 or sglang>=0.4.6.post1; Ollama, LM Studio, MLX-LM, llama.cpp and KTransformers supported. 1M mode needs vLLM DUAL_CHUNK_FLASH_ATTN backend and about 240 GB of GPU memory per the card.

Apache-2.0. Apache 2.0: commercial use, modification and redistribution allowed with notice; no usage caps.

Model card on Hugging Face

Design a Qwen3-30B-A3B-Instruct-2507 deployment

Preloaded with Qwen3-30B-A3B-Instruct-2507. Add your ERP and documents, change GPUs or users, and export the diagram.

Loading the architecture builder...

Questions

How much VRAM does Qwen3-30B-A3B-Instruct-2507 need?

The weights alone take about 61.0 GB in BF16, 30.5 GB in FP8 and 17.1 GB in 4-bit. On top of that each request holds a KV cache of about 0.40 GB at 8K tokens of context (FP8 cache), so 20 people generating at once need roughly 8.05 GB more, plus a few GB of runtime overhead.

What is the smallest GPU setup that runs Qwen3-30B-A3B-Instruct-2507?

For a single user at 8K context in FP8, 1 x NVIDIA A100 40GB PCIe (40 GB each) fits, at an estimated 153 tokens per second. For a team, size for concurrent requests and context; the builder above does that.

Is Qwen3-30B-A3B-Instruct-2507 allowed for commercial use?

Qwen3-30B-A3B-Instruct-2507 is released under Apache-2.0. Apache 2.0: commercial use, modification and redistribution allowed with notice; no usage caps. Check the licence text on the model card with your legal team before production use.

Which engine should serve Qwen3-30B-A3B-Instruct-2507 on-prem?

vllm>=0.8.5 or sglang>=0.4.6.post1; Ollama, LM Studio, MLX-LM, llama.cpp and KTransformers supported. 1M mode needs vLLM DUAL_CHUNK_FLASH_ATTN backend and about 240 GB of GPU memory per the card.