How to run Qwen 3 32B on NVIDIA GeForce RTX 3090

This tutorial walks you through running Qwen 3 32B on an NVIDIA GeForce RTX 3090. Exact commands, expected tokens-per-second, and the tradeoffs you should know before starting.

Does it fit?

NVIDIA GeForce RTX 3090 has 24 GB of GDDR6X. Qwen 3 32B at q4_K_M wants ~22 GB of it for weights alone.

Verdict: ✅ Fits natively. Expect ~30-45 tok/s on first-token latency after warm-up.

Install Ollama (the easy path)

# macOS/Linux
curl -fsSL https://ollama.com/install.sh | sh
ollama pull qwen3:32b
ollama run qwen3:32b

Ollama handles GPU detection automatically on NVIDIA (via CUDA), AMD (via ROCm on Linux), and Apple Silicon (via Metal). No manual configuration needed.

Install llama.cpp (more control)

llama.cpp gives you flag-level control over quantization, context length, and layer offload. Build from source:

git clone https://github.com/ggerganov/llama.cpp
cd llama.cpp
make GGML_CUDA=1 -j

# Download a quantized GGUF (community favorite: bartowski or TheBloke on HuggingFace)
./llama-cli -m ~/models/qwen-3-32b-q4_k_m.gguf \
 -n 512 -c 4096 \
 -ngl 999 \
 -p "Write a haiku about GPUs"

-ngl 999 offloads all layers to the GPU.

Expected performance

• Community reports from LocalLLaMA suggest ~25-40 tok/s on this class of hardware.

For single-user chat these speeds feel instant. For RAG pipelines where the model re-reads long context, prefill throughput matters more than generation tok/s.

Common issues

"out of memory" on the first prompt: reduce context length (-c 2048) or quantization (q4_K_S instead of q4_K_M).

Slow first token but fast generation: that's prompt processing ("prefill"). Normal — blame the KV cache building. Subsequent messages in the same session will be snappy.

Frequent swapping / system hangs: VRAM is full AND system RAM is full. Close Chrome. Add more DDR5.

Related

• Full NVIDIA GeForce RTX 3090 benchmarks →
• Best GPU for Qwen 3 32B →
• AI Rigs buyer's guide →

NVIDIA GeForce RTX 3090 specs: 24GB memory, 350W TDP, 2020 launch. MSRP $1,499.

Does it fit? Full quantization matrix

Weight-only VRAM for Qwen 3 32B at every common quant, plus the KV-cache overhead for a 4K-token context. KV cache scales linearly with context — see the context-length table further down.

Values are approximate — actual footprint depends on batch size, whether the KV cache is quantized (-ctk q8_0 -ctv q8_0 in llama.cpp halves it), and whether you reserve VRAM for a display. Rule of thumb: budget 5-10% headroom on top of the table.

How public benchmarks show and compared

Every tok/s, FPS, and synthetic score in this article is pulled live from the SpecPicks benchmark catalog (hardware_specs, ai_benchmarks, synthetic_benchmarks). We cite the source_name on each row — the vast majority are community-reported numbers from r/LocalLLaMA and llama.cpp GitHub Discussions, with synthetic scores from PassMark, Phoronix, and Tom's Hardware's GPU hierarchy.

Where DB rows exist for a specific model+quant+GPU combination, we quote the number exactly. Where they don't, we fall back to published spec-sheet values (VRAM capacity, TDP, memory bandwidth) plus the closest community-verified ballpark — clearly flagged as a ballpark, not a measurement. We prefer "we don't know" over a fabricated number.

SpecPicks does not run paid hardware review cycles; we aggregate. If you see a number you can improve on, pull-request the row.

Measured tok/s on this GPU

Live data from ai_benchmarks for NVIDIA GeForce RTX 3090, filtered to the Qwen 3 32B family where available:

We don't yet have a verified Qwen 3 32B measurement on this specific card in ai_benchmarks. Community reports on r/LocalLLaMA cluster around 25-40 tok/s at q4_K_M; we'll backfill the table once a confirmed row lands.

For the full tok/s matrix on this card across every model we've logged, see the NVIDIA GeForce RTX 3090 benchmark page.

Context length and VRAM — the hidden cost

KV cache grows linearly with context. Here's the approximate overhead on top of 19.2 GB of q4_K_M weights for Qwen 3 32B:

For long-context workloads (32K and above) on consumer hardware, use llama.cpp's KV-cache quantization — -ctk q8_0 -ctv q8_0 roughly halves cache footprint with sub-1% quality loss. This is the single biggest VRAM-saving flag for long context.

Perf-per-dollar / perf-per-watt

At MSRP of $1,499 and a 350 W TDP, perf-per-dollar and perf-per-watt are (Qwen 3 32B gen tok/s) ÷ 1.499 and (gen tok/s) ÷ 3.5 respectively. We'll fill in the absolute numbers once a verified Qwen 3 32B measurement on this card lands in ai_benchmarks.

Use these numbers only when comparing like-for-like single-user inference. Batched serving (vLLM, TensorRT-LLM) changes the math — higher throughput per card, but it no longer maps to chat tok/s.

Which runtime wins on this hardware?

Three mainstream runtimes target NVIDIA GeForce RTX 3090; the right one depends on your workload:

• Ollama — easiest. Auto-detects CUDA, handles model downloads, exposes an OpenAI-compatible API out of the box. Wraps llama.cpp; you give up fine-grained control for zero setup.
• llama.cpp — direct flag-level control over quant, context, KV-cache precision, batch size, split layers across GPUs. Where the LocalLLaMA community benchmarks its numbers (see the Apple-Silicon megathread #4167 for reference tok/s across M-series chips).
• vLLM — built for production serving. Tensor parallelism, PagedAttention, continuous batching. Linux + NVIDIA CUDA primary target. If you're not serving multiple concurrent users, the overhead isn't worth it.

For head-to-head numbers and install commands across all three, see our Ollama vs llama.cpp vs vLLM guide.

Troubleshooting — three failure modes and fixes

1. First token takes 5-30 seconds, then generation is fast. That's normal prefill: the model is processing your prompt before it can start generating. On a long prompt (4K+ tokens) prefill dominates the first-token latency. If it's unexpectedly slow, check that you actually offloaded layers to the GPU — nvidia-smi or powermetrics (macOS) should show near-100% utilisation during prefill. If utilisation is flat, your inference is running on CPU.

2. "Out of memory" halfway through a long chat. The KV cache grew past what the card can hold. Drop to a smaller quant (q4_K_M → q3_K_M), cut -c context length, or enable KV-cache quantization (-ctk q8_0 -ctv q8_0 in llama.cpp). On Ollama set num_ctx smaller in your Modelfile.

3. Tok/s is ~30% of what LocalLLaMA threads report. Three usual suspects: (a) power/thermal throttling — check sustained clocks during a long prompt; (b) PCIe x8 or x4 link when you expected x16 — nvidia-smi --query-gpu=pcie.link.width.current --format=csv; (c) running the wrong binary, e.g. a non-CUDA llama.cpp build on an NVIDIA card. Rebuild with GGML_CUDA=1 and confirm.

Sources

1. r/LocalLLaMA (community tok/s threads)
2. llama.cpp GitHub Discussions #4167 — Apple Silicon benchmark thread
3. Tom's Hardware GPU Hierarchy

Related guides

• NVIDIA GeForce RTX 3090 full benchmark page
• Best GPU for Qwen 3 32B
• Ollama vs llama.cpp vs vLLM
• What VRAM do you need for local LLMs?

Products mentioned

• ASUS TUF Gaming NVIDIA GeForce RTX 3090 OC Edition Graphi…