LLM

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

1.7B
Parameters
BF16
Native precision
32K tokens (32,768)
Context length
Apache 2.0
License
Text
Modality
Alibaba (Qwen)
Organization

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.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
BF163.2 GB3.8 GBRTX 30701$0.088/hr
FP8 (quantized)1.6 GB1.9 GBRTX 5060 Ti1$0.145/hr
INT4 (quantized)0.8 GB1.0 GBRTX 30701$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.

ContextKV cache, one sequence
4K0.44 GB
32K3.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 1

Run Qwen3-1.7B-Base with Ollama

Verified against Ollama's own library listing.

ollama run qwen3:1.7b

Source: https://ollama.com/library/qwen3:1.7b

Run 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-GGUF

Source: 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.

  1. Launch a bare GPU pod sized to the requirement above (1× RTX 3070 or larger).
  2. 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.
  3. Run the command and connect to the resulting endpoint.
Launch a GPU pod

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More Qwen3 models

All 105 Qwen3 models: VRAM and GPU requirements

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.

More on Qwen3-1.7B-Base

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

Connect your accounts

One console for the GPU clouds you already use.

Connect your accounts for $20 a month, flat. Your provider bills the GPU.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.