How to Deploy Qwen3.6 27B Locally
Qwen3.6 27B is a dense model with 27.8B parameters. At Q4 it needs at least 19GB of VRAM, and 24GB is the comfortable amount for an 8K context. The cheapest card that runs it today is the Tesla V100 32GB at about $1,141, at roughly 36.3 tokens/s.
Qwen3.6 27B details
How much VRAM does Qwen3.6 27B need for local deployment?
| Quantization | WeightsGB | Total at 8KGB | Total at 32KGB | Total at 128KGB |
|---|---|---|---|---|
| 1-bit | 6.5est. | 9.5 | 15.5 | 39.5 |
| 2-bit | 11.8GGUF | 13.3 | 19.3 | 43.3 |
| 3-bit | 14.5GGUF | 16.3 | 22.3 | 46.3 |
| 4-bit | 16.8GGUF | 18.5 | 24.5 | 48.5 |
| 5-bit | 19.5GGUF | 21.7 | 27.7 | 51.7 |
| 8-bit | 28.6GGUF | 31.8 | 37.8 | 61.8 |
| FP16 | 53.8GGUF | 57.3 | 63.3 | 87.3 |
Total = weights + KV cache (FP16) + 1GB runtime overhead. Weights marked GGUF are measured file sizes from the repository; the rest are estimated from bytes per parameter. Contexts beyond this model's 256K limit show a dash. Each tier takes whichever file of that bit width the repository has, preferring unsloth dynamic quants, so the exact file name varies by model.
Which GPUs can run Qwen3.6 27B?
AmazonJP
| Device | VRAMGB | Price | Est. t/s | Suggested context |
|---|---|---|---|---|
| 32 | $1,1413 listings | 36.3 | 32K | |
| 24 | $1,1643 listings | 12.1 | 8K | |
| 20 | $1,2449 listings | 23.3 | 8K | |
| 24 | $1,7389 listings | 27.9 | 8K | |
| 32 | $2,0743 listings | 16 | 32K | |
| 32 | $2,2446 listings | 18.7 | 32K | |
| 24 | $2,5209 listings | 37.8 | 8K | |
| 128 | $3,9136 listings | 7.6 | 128K | |
| 24 | $3,9565 listings | 27.3 | 8K | |
| 24 | $4,9059 listings | 40.6 | 8K | |
| 32 | $7,4899 listings | 70.3 | 32K | |
| 128 | $8,2233 listings | 11.2 | 128K | |
| 22 | —No listings | 25.1 | 8K | |
| 24 | —No listings | 53.5 | 8K | |
| 32 | —No listings | 16 | 32K | |
| 32 | —No listings | 29.9 | 32K | |
| 32 | —No listings | 70.3 | 32K | |
| 32 | —No listings | 35.5 | 32K | |
| 32 | —No listings | 29.7 | 32K | |
| 32 | —No listings | 16.9 | 32K | |
| 32 | —No listings | 36.2 | 32K | |
| 40 | —No listings | 61.5 | 32K | |
| 40 | —No listings | 61.7 | 32K | |
| 48 | —No listings | 40.6 | 32K | |
| 48 | —No listings | 25.1 | 32K | |
| 48 | —No listings | 53.5 | 32K | |
| 64 | —No listings | 59.1 | 128K | |
| 64 | —No listings | 46.8 | 128K | |
| 72 | —No listings | 53.5 | 128K | |
| 84 | —No listings | 62 | 128K | |
| 96 | —No listings | 70.3 | 128K | |
| Mac Studio M4 Max 128GB | 128 | —No listings | 17.6 | 128K |
| Mac Studio M5 Max 128GB | 128 | —No listings | 19.7 | 128K |
| MacBook Pro M4 Max 128GB | 128 | —No listings | 17.6 | 128K |
| MacBook Pro M5 Max 128GB | 128 | —No listings | 19.7 | 128K |
| Mac Studio M3 Ultra 512GB | 512 | —No listings | 26.2 | 128K |
Fits when weights + KV cache + runtime overhead is at or below usable memory, single card. "Offload" on MoE models means it runs with expert weights in system RAM (only attention layers and KV cache stay in VRAM); that speed assumes 70 GB/s RAM bandwidth. The context column is the largest tier that fits.
Deploy Qwen3.6 27B locally with Ollama, llama.cpp or vLLM
The Ollama library has no official tag for it yet.
llama.cpp pulls the GGUF straight from Hugging Face; -c sets the context length.
llama-server -hf unsloth/Qwen3.6-27B-GGUF:Q4_K_M -c 8192
vLLM serves the original-precision weights, which needs far more memory than GGUF and usually more than one GPU.
vllm serve Qwen/Qwen3.6-27B
File names follow that week's model-library snapshot; the definitions are in the methodology. Methodology
FAQ
How much VRAM does Qwen3.6 27B need?
At Q4_K_M with an 8K context Qwen3.6 27B needs about 19GB of VRAM; 24GB leaves comfortable headroom.
What is the cheapest GPU that runs Qwen3.6 27B?
The Tesla V100 32GB: 32GB of VRAM, currently about $1,141, at roughly 36.3 tokens/s.
Can you run Qwen3.6 27B with Ollama?
Not yet: the Ollama library has no official tag for it. You can load the GGUF with llama.cpp instead.