Model library / Chat / reasoning
Qwen3 Coder 30B: GPU requirements and hosting
A mixture-of-experts checkpoint built for coding and tool use. Evaluate it against repository tasks with checkable outcomes, such as passing tests or a correct patch.
Sources reviewed 2026-09-30 · B3IQ engineering
Checkpoint overview.
Model creator
Qwen team, Alibaba Cloud- Task in catalog
- Chat / reasoning
- Approx. total parameters (catalog)
- 30B
- Runtime families
- ollama
- Model license
- Apache-2.0 ↗
- Upstream access at review
- No repository access gate reported
- Canonical checkpoint
- Qwen/Qwen3-Coder-30B-A3B-Instruct ↗
The creator identifies the original checkpoint. Runtime profiles may use separately packaged artifacts; their publishers and configuration can differ. Check the selected profile below.
Runtime profiles and requirements
Active parameters do not equal the weights you must store. Plan memory for the full checkpoint and validate long-context behavior on the runtime you choose.
ollama · qwen3-coder-30b
- Catalog GPU threshold
- 32 GB
- Configured context
- 8,192 tokens
- Catalog system RAM
- 64 GB
- Runtime
- ollama
- Artifact identifier
qwen3-coder:30b- Precision
- Not pinned in catalog
- Configured concurrency
- 1 request(s)
- Profile inputs / outputs
- text → text
- Deployed artifact revision
- Not verified
Catalog thresholds are configuration guidance, not measured peak memory. A positive GPU requirement is not recorded for every profile; unspecified is not zero. Context, concurrency and runtime overhead can increase memory use. Configured context is a profile setting, not the upstream maximum. Concurrency is configuration, not a load-test result.
Weight-only arithmetic and a planning estimate
Using the catalog's approximate 30B total parameters, 16-bit weights alone occupy about 60 GB (parameters × 2 bytes). The shared sizing helper rounds a 20% planning reserve to 72 GB.
This arithmetic does not describe the selected quantized artifact. It excludes a workload-specific KV-cache calculation and cannot guarantee fit at the configured context or concurrency. A mixture-of-experts model still stores its full weights.
See the assumptions →Plan the machine.
Memory-based machine candidates depend on the current visible store configurations. Confirm runtime compatibility, GPU count, interconnect and workload before purchase. Pricing and availability are shown on the machine page.
Explore machinesBefore deployment
Test the workload you need.
Include tool definitions, source files and tool results in the context budget. Use the checkpoint's chat and tool-call format when testing your agent.
These are catalog profiles and planning figures. No B3IQ performance measurement or live capacity is claimed. Confirm the artifact, runtime, workload and machine before deployment.
Evidence available
- Upstream identity / license
- Source reviewed
- Runtime settings
- Catalog configuration
- Memory fit
- Guidance; not a measured peak
- B3IQ performance
- No published benchmark
- Installation / live capacity
- Confirm for your machine
Source and access.
- Upstream checkpoint
- Qwen/Qwen3-Coder-30B-A3B-Instruct ↗
- Upstream license metadata
- Apache-2.0 ↗
- Access
- No access gate reported by the upstream repository at review.
- Reviewed source revision
b2cff646eb4bb1d68355c01b18ae02e7cf42d120↗
The reviewed revision identifies the source used for this guide. It is not a claim that this revision is installed on a B3IQ machine. Review the publisher's current license and acceptable-use terms for your application.
Guide updates and corrections.
These are changes to the guide. Source-review dates and workload-test evidence are recorded separately.
- · Update
Added creator attribution and a canonical checkpoint overview. The guide now explains how the original creator differs from a runtime artifact publisher.
To report a correction, send the affected claim and a source URL to hello@b3iq.org.
Continue your evaluation.
Compare another checkpoint or explore a complementary task. Each guide explains the workload it is intended for.