24 Feb 2026
Qwen3.5-27B
Dense compute alongside a sparse sibling
27B reported total · text + image + video
Qwen / Dense
Qwen3.5-9B
Test whether the middle size earns its memory
New to model sizes or GPU memory? Start with weights, parameters and quantization →
The 9B model sits between small-device experiments and the 27B tier. Compare it with 4B on the errors that matter, then use 27B to see how much quality remains on the table.
9Breported total parameters
Denseactive parameters per token
262,144configured token positions
Publisher-reported, rounded model count; not an exact tensor census. Multimodal components and packaging can change the artifact size.
Evaluate it for
Constrained text and visual tasks with task-specific acceptance tests.
Choose another path when
An 18 GB BF16 estimate can look comfortable on a 24 GB device until long requests or concurrency consume the remainder.
Release context
Why this release matters
The March release brought the Qwen3.5 hybrid multimodal design to four dense sizes. This matters because the same family can support a controlled quality-versus-memory study, rather than a comparison across unrelated prompts and templates.
Deployment starting points
Which hardware, how many, at what precision?
Start with an exact artifact and an engine that supports it. A configuration below is evidence of a documented path; its device count does not promise a particular throughput or concurrency.
No certified hardware configuration in this edition
An 18 GB BF16 estimate can look comfortable on a 24 GB device until long requests or concurrency consume the remainder.
The pinned model card establishes the architecture. It does not, by itself, prove that a particular GPU count runs this checkpoint at your target context. The capacity screen below helps rule out undersized allocations; a successful load and workload test are still required.
19.31 GB of tensor data in the pinned index
This is the index’s reported tensor payload, in decimal GB. It excludes file headers and runtime memory. Mixed precision, conversion and host/device placement determine how much GPU memory the loaded model needs.
Inspect the exact index metadata →Capacity screen: would the weights fit?
This estimates inference memory for a hypothetical uniform precision. It is useful for rejecting an allocation that is too small. It does not establish a working deployment or estimate training memory.
| Representation | Approximate weight floor | What remains to budget |
|---|---|---|
| 16-bit uniform | 18 GB | Cache, modality state, workspace, quantization metadata and uneven sharding |
| 8-bit uniform | 9 GB | Cache, modality state, workspace, quantization metadata and uneven sharding |
| 4-bit uniform | 4.5 GB | Cache, modality state, workspace, quantization metadata and uneven sharding |
Enter the total across the whole model replica, not per GPU: KV or recurrent cache for all concurrent requests, image/audio state and execution workspace. There is no universal default. We additionally leave 15% of each GPU unused.
18 GB for hypothetical weights
Enter a request-and-buffer budget to calculate the aggregate capacity requirement.
A count of one does not prove the engine supports this GPU. A count above one does not prove the model shards evenly or communicates efficiently. Publisher-reported, rounded model count; not an exact tensor census. Multimodal components and packaging can change the artifact size.
Architecture in practice
What the serving engine has to do
Two kinds of layers retain two kinds of state.
Hybrid attention does not mean zero request state.
A full-attention formula cannot describe every layer.
Mechanism schematic based on the pinned model card and configuration. It explains a design principle; it is not a full implementation graph.
Inspect the full checkpoint specifications
| Exact checkpoint | Qwen/Qwen3.5-9B |
|---|---|
| Text model type | qwen3_5_text |
| Layers | 32 |
| Hidden width | 4,096 |
| Attention / KV heads | 16 / 4 |
| Head dimension | 256 |
| Routed / selected experts | Not verified / Not verified |
| Configured positions | 262,144 |
| Documented extension | 1,010,000 tokens; additional configuration and evaluation required |
| Inputs → output | text, image, video → text |
| License metadata | apache-2.0 |
24 linear attention layers; 8 full attention layers. These counts describe the configured pattern.
Open weights do not imply unrestricted use. Read the applicable license terms linked from the pinned card.
A useful comparison
What else belongs on the shortlist?
Compare the next dense size first; the MoE provides a different compute/storage tradeoff.
24 Feb 2026
Qwen3.5-35B-A3B
The easiest MoE memory lesson to make concrete
35B reported total · text + image + video
These are editorial comparison candidates. We have not run a matched quality or serving benchmark, so this is not a ranking.
Prepare to explain it
The interview lesson
Calculate the weight floor, then identify what grows with prompt length and concurrent requests.
Attention layouts · Quantization · Courses and worked examples
For a deployment evaluation, record exact weights, precision, engine, device count, interconnect, prompt/output lengths and concurrency. Report task success, errors, TTFT, TPOT and useful throughput together.
Sources and citation
Our assessment is editorial judgment based on the linked architecture and deployment evidence. Model facts are publisher-reported or attributed to runtime maintainers; no independent GPU benchmark was run.
AI Infra Interviews, “Qwen3.5-9B: release, architecture and deployment”, checked 2026-09-13. Preserve this date and the exact checkpoint when citing.