What GPU do I need to run Qwen/Qwen3-1.7B-Base?
A 1.7B language model for chat and instruction-following. 1.7B parameters, published in BF16. View on Hugging Face
Qwen3-1.7B-Base is published by Qwen on Hugging Face, with 1,911,362 downloads and 77 likes to date. It's a Qwen3ForCausalLM model built for text-generation, published natively in BF16.
What Qwen3-1.7B-Base is
Qwen3-1.7B-Base is a 1.7B-parameter language model published by Alibaba (Qwen) on Hugging Face. It is released under Apache 2.0.
License note: fully permissive, no gating and no usage restrictions. Facts in this section are sourced from Qwen3-1.7B-Base's Hugging Face model card, not benchmarked by Aquanode.
What it's used for
- Chat assistants
- Instruction following
- Synthetic data generation
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.
| Precision | Weight size | Required VRAM | Cheapest live fit | GPUs needed | Est. $/hr (full fit) |
|---|---|---|---|---|---|
| BF16 | 3.2 GB | 3.8 GB | RTX 3070 | 1 | $0.088/hr |
| FP8 (quantized) | 1.6 GB | 1.9 GB | RTX 5060 Ti | 1 | $0.145/hr |
| INT4 (quantized) | 0.8 GB | 1.0 GB | RTX 3070 | 1 | $0.088/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 Qwen3-1.7B-Base at its published (BF16) precision: 1× RTX 3070, at $0.088/hr per GPU ($0.088/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.
Qwen3-1.7B-Base: 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.
Grouped-query attention: every layer caches keys and values for a few shared KV heads. Cached per token: 114,688 bytes at 16-bit.
| Context | KV cache, one sequence |
|---|---|
| 4K | 0.44 GB |
| 32K | 3.5 GB |
Computed from the layer, head and window counts in the model's own configuration (Qwen/Qwen3-1.7B-Base), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.
Qwen3-1.7B-Base: common questions
How much VRAM does Qwen3-1.7B-Base need?
3.8 GB at BF16, 1.9 GB at FP8 (quantized), 1.0 GB at INT4 (quantized). All of those sit under 6 GB, the smallest capacity this page reasons about, so VRAM is not what limits where this model runs. The 3.2 GB of weights plus inference overhead is the whole requirement.
How many copies of Qwen3-1.7B-Base fit on one RTX 3070?
2, by VRAM alone. That card carries 8.0 GB and one copy needs 3.8 GB at BF16, on a live rate of $0.088/hr for the whole card. Throughput is not modelled here, so 2 copies is not 2 times the requests served.
How to run Qwen3-1.7B-Base
Run Qwen3-1.7B-Base with vLLM
Generic example, not from the model's own docs: adjust flags (quantization, context length, parallelism) for your setup.
vllm serve Qwen/Qwen3-1.7B-Base --tensor-parallel-size 1Run Qwen3-1.7B-Base with Ollama
Verified against Ollama's own library listing.
ollama run qwen3:1.7bRun Qwen3-1.7B-Base with GGUF quantizations
Prebuilt GGUF weights published at mradermacher/Qwen3-1.7B-Base-GGUF. Run with llama.cpp's llama-server or load the repo directly in LM Studio.
llama-server -hf mradermacher/Qwen3-1.7B-Base-GGUFSource: https://huggingface.co/mradermacher/Qwen3-1.7B-Base-GGUF
Deploy Qwen3-1.7B-Base on Aquanode
Aquanode has no one-click deploy template for Qwen3-1.7B-Base; you install the inference engine yourself with the commands below. Aquanode sells GPU pods billed per second, not a hosted inference API.
- Launch a bare GPU pod sized to the requirement above (1× RTX 3070 or larger).
- Open a terminal on the pod, or save one of the commands above as a startup script so it runs automatically the first time the pod boots.
- Run the command and connect to the resulting endpoint.
Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.
More Qwen3 models
- Qwen3-1.7B-MLX-bf16 (1.7B, BF16)
- Qwen3-1.7B-GLB-3D-Coder (1.7B, F16)
- Qwen3-1.7B (2.0B, BF16)
- Qwen3-1.7B-FP8 (2.0B, F8_E4M3)
- Qwen3-0.6B-FP8 (752M, F8_E4M3)
Lineage
Quantized and fine-tuned versions
Alternatives at this size
Other models for text-generation within about a third of Qwen3-1.7B-Base's 1.7B parameters, from other model lines.
- Llama-3.2-1B-Instruct (1.2B, BF16)
- OLMo-2-0425-1B (1.5B, F32)
- LFM2.5-1.2B-Instruct (1.2B, BF16)
- SmolLM2-1.7B (1.7B, BF16)
- h2ovl-mississippi-2b (2.2B, BF16)
More on Qwen3-1.7B-Base
Fits on an 8 GB GPU at BF16: every model that fits in 8 GB.
Related reading: RTX 3070 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.
Your own GPU cloud accounts
One console for the GPU clouds you already rent from. Your keys stay on your machine.
$20 a month, flat