What can NVIDIA GeForce RTX 4080 Super run for coding?

Build: RTX 4080 Super + i7-14700K + 32GB DDR5

Memory: 16 GB VRAM + 32 GB system RAM
Runner: llama.cpp / Ollama (CUDA)

Runs comfortably
60 models

Ranked by fit for coding use case + predicted speed. Click a row for VRAM breakdown.

#1CodeGemma 7B
7B
gemma
Commercial OK
Quant: Q4_K_MContext: 8,192VRAM: 9.7 GBHeadroom: 6.3 GBTTFT: fast
ollama run codegemma:7b
113
tok/s
Estimated
Weights
4.20 GB
KV cache
3.50 GB
Activations
0.22 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~343 ms (fast)
#2Qwen 3 8B
8B
qwen
Commercial OK
Quant: Q4_K_MContext: 8,192VRAM: 10.8 GBHeadroom: 5.2 GBTTFT: fast
ollama run qwen3:8b
99
tok/s
Estimated
Weights
4.80 GB
KV cache
4.00 GB
Activations
0.25 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~392 ms (fast)
#3Qwen 2.5 7B Instruct
7B
qwen
Commercial OK
Quant: Q8_0Context: 8,192VRAM: 10.8 GBHeadroom: 5.2 GBTTFT: fast
ollama run qwen2.5:7b
64
tok/s
Estimated
Weights
8.10 GB
KV cache
0.47 GB
Activations
0.41 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~343 ms (fast)
#4Llama 3.1 8B Instruct
8B
llama
Commercial OK
Quant: Q8_0Context: 8,192VRAM: 11.8 GBHeadroom: 4.2 GBTTFT: fast
ollama run llama3.1:8b
56
tok/s
Estimated
Weights
8.50 GB
KV cache
1.07 GB
Activations
0.43 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~392 ms (fast)
#5Qwen 2.5 Coder 3B
3B
qwen
Commercial OK
Quant: Q4_K_MContext: 8,192VRAM: 5.3 GBHeadroom: 10.7 GBTTFT: fast
264
tok/s
Estimated
Weights
1.90 GB
KV cache
1.50 GB
Activations
0.10 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~147 ms (fast)
#6StarCoder 2 3B
3B
other
Commercial OK
Quant: Q4_K_MContext: 8,192VRAM: 5.4 GBHeadroom: 10.6 GBTTFT: fast
264
tok/s
Estimated
Weights
2.00 GB
KV cache
1.50 GB
Activations
0.11 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~147 ms (fast)
#7Codestral Mamba 7B
7B
mistral
Commercial OK
Quant: Q4_K_MContext: 8,192VRAM: 9.7 GBHeadroom: 6.3 GBTTFT: fast
113
tok/s
Estimated
Weights
4.20 GB
KV cache
3.50 GB
Activations
0.22 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~343 ms (fast)
#8StarCoder 2 7B
7B
other
Commercial OK
Quant: Q4_K_MContext: 8,192VRAM: 9.9 GBHeadroom: 6.1 GBTTFT: fast
113
tok/s
Estimated
Weights
4.40 GB
KV cache
3.50 GB
Activations
0.23 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~343 ms (fast)
#9OpenCoder 8B
8B
opencoder
Commercial OK
Quant: Q4_K_MContext: 8,192VRAM: 10.7 GBHeadroom: 5.3 GBTTFT: fast
99
tok/s
Estimated
Weights
4.70 GB
KV cache
4.00 GB
Activations
0.24 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~392 ms (fast)
#10Yi Coder 9B
9B
yi
Commercial OK
Quant: Q4_K_MContext: 8,192VRAM: 12.0 GBHeadroom: 4.0 GBTTFT: fast
88
tok/s
Estimated
Weights
5.40 GB
KV cache
4.50 GB
Activations
0.28 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~441 ms (fast)
#11Llama 3.2 3B Instruct
3B
llama
Commercial OK
Quant: Q8_0Context: 8,192VRAM: 6.9 GBHeadroom: 9.1 GBTTFT: fast
ollama run llama3.2:3b
150
tok/s
Estimated
Weights
3.40 GB
KV cache
1.50 GB
Activations
0.18 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~147 ms (fast)
#12Phi-3.5 Vision
4.2B
phi
Commercial OK
Quant: Q4_K_MContext: 8,192VRAM: 6.5 GBHeadroom: 9.5 GBTTFT: fast
189
tok/s
Estimated
Weights
2.50 GB
KV cache
2.10 GB
Activations
0.13 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~206 ms (fast)

Runs with tradeoffs
46 models

Tight VRAM, partial CPU offload, or context-limited.

DeepSeek Coder V2 Lite (16B)
16B
deepseek
Commercial OK
Quant: Q4_K_MContext: 2,048VRAM: 13.8 GBHeadroom: 2.2 GBTTFT: noticeable
  • • Tight VRAM fit — only 2.2 GB headroom left for context growth
ollama run deepseek-coder-v2:16b
50
tok/s
Estimated
Weights
9.50 GB
KV cache
2.00 GB
Activations
0.48 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~785 ms (noticeable)
Qwen 3 14B
14B
qwen
Commercial OK
Quant: Q4_K_MContext: 2,048VRAM: 12.4 GBHeadroom: 3.6 GBTTFT: noticeable
  • • Tight VRAM fit — only 3.6 GB headroom left for context growth
ollama run qwen3:14b
57
tok/s
Estimated
Weights
8.40 GB
KV cache
1.75 GB
Activations
0.42 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~687 ms (noticeable)
Qwen 2.5 14B Instruct
14B
qwen
Commercial OK
Quant: Q4_K_MContext: 2,048VRAM: 12.9 GBHeadroom: 3.1 GBTTFT: noticeable
  • • Tight VRAM fit — only 3.1 GB headroom left for context growth
ollama run qwen2.5:14b
57
tok/s
Estimated
Weights
8.90 GB
KV cache
1.75 GB
Activations
0.45 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~687 ms (noticeable)
Codestral 22B
22B
mistral
Quant: Q4_K_MContext: 8,192VRAM: 26.5 GBHeadroom: 8.7 GBTTFT: noticeable
  • • Partial CPU offload: ~40% of layers run on CPU
  • • CPU is the bottleneck — upgrading RAM bandwidth helps more than VRAM here
ollama run codestral:22b
5
tok/s
Estimated
Weights
13.00 GB
KV cache
11.00 GB
Activations
0.66 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~1079 ms (noticeable)
Qwen 2.5 Coder 14B Instruct
14B
qwen
Commercial OK
Quant: Q4_K_MContext: 2,048VRAM: 12.4 GBHeadroom: 3.6 GBTTFT: noticeable
  • • Tight VRAM fit — only 3.6 GB headroom left for context growth
57
tok/s
Estimated
Weights
8.40 GB
KV cache
1.75 GB
Activations
0.42 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~687 ms (noticeable)
StarCoder 2 15B
15B
other
Commercial OK
Quant: Q4_K_MContext: 2,048VRAM: 13.1 GBHeadroom: 2.9 GBTTFT: noticeable
  • • Tight VRAM fit — only 2.9 GB headroom left for context growth
53
tok/s
Estimated
Weights
9.00 GB
KV cache
1.88 GB
Activations
0.45 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~736 ms (noticeable)
Qwen 2.5 Coder 32B Instruct
32B
qwen
Commercial OK
Quant: Q4_K_MContext: 8,192VRAM: 23.9 GBHeadroom: 11.3 GBTTFT: noticeable
  • • Partial CPU offload: ~33% of layers run on CPU
  • • CPU is the bottleneck — upgrading RAM bandwidth helps more than VRAM here
ollama run qwen2.5-coder:32b
4
tok/s
Estimated
Weights
19.00 GB
KV cache
2.15 GB
Activations
0.96 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~1569 ms (noticeable)
Qwen 3 30B-A3B
30B
qwen
Commercial OK
Quant: Q4_K_MContext: 2,048VRAM: 24.5 GBHeadroom: 10.7 GBTTFT: noticeable
  • • Partial CPU offload: ~35% of layers run on CPU
  • • CPU is the bottleneck — upgrading RAM bandwidth helps more than VRAM here
ollama run qwen3:30b
4
tok/s
Estimated
Weights
18.00 GB
KV cache
3.75 GB
Activations
0.90 GB
Runtime
1.80 GB
Time to first token (prefill, 512-token prompt): ~1471 ms (noticeable)

What if you upgraded?

Hypothetical scenarios. We re-ran the compatibility engine for each.

+32 GB system RAM

Check the current price

Adds 32 GB to your CPU-offload working set. Helps when models don't quite fit in VRAM.

Unlocks: 28 new comfortable, 57 new tradeoff

  • • Qwen 3 0.6B
  • • Qwen 3 1.7B
  • • Gemma 3 270M
  • • SmolLM2 135M Instruct

Upgrade to NVIDIA RTX 2080 Ti 22GB (China-mod)

Check the current price

22 GB VRAM (vs your 16 GB) plus a bandwidth jump from ~736 GB/s to ~616 GB/s.

Unlocks: 47 new comfortable

  • • Qwen 3 0.6B
  • • Qwen 3 14B
  • • Qwen 3 1.7B
  • • Gemma 3 270M

Add a second NVIDIA GeForce RTX 4080 Super

Launch MSRP $999 (2024). Check the current price.

Tensor parallelism splits the model across both cards, effectively doubling VRAM. Bandwidth doesn't double — runs ~1.5× the single-card speed in practice.

Unlocks: 68 new comfortable

  • • Qwen 3 0.6B
  • • Qwen 3 30B-A3B
  • • Qwen 2.5 Coder 32B Instruct
  • • Qwen 3 32B

Some links above are affiliate links. We may earn a commission at no extra cost to you. How we make money.

Won't run
top 5 popular models

Need more memory than you have. Shown for orientation.

DeepSeek V4 Pro (1.6T MoE)
1600B
deepseek
Commercial OK

Even with CPU offload, needs more memory than your VRAM (16 GB) + 60% of system RAM (19 GB) combined.

—
Qwen 3 235B-A22B
235B
qwen
Commercial OK

Even with CPU offload, needs more memory than your VRAM (16 GB) + 60% of system RAM (19 GB) combined.

—
DeepSeek R1 (671B reasoning)
671B
deepseek
Commercial OK

Even with CPU offload, needs more memory than your VRAM (16 GB) + 60% of system RAM (19 GB) combined.

—
Llama 4 Scout
109B
llama
Commercial OK

Even with CPU offload, needs more memory than your VRAM (16 GB) + 60% of system RAM (19 GB) combined.

—
DeepSeek V4 Flash (284B MoE)
284B
deepseek
Commercial OK

Even with CPU offload, needs more memory than your VRAM (16 GB) + 60% of system RAM (19 GB) combined.

—
Cloud GPU rental

Not enough VRAM for these models? Rent a GPU by the hour

The models above need more memory than 16 GB VRAM + 32 GB system RAM. You can rent a GPU with enough VRAM by the hour to run one of them, or to test it before you buy hardware. For daily use, owning a card usually costs less over time.

RunPod

billed per GPU-hour

Hourly GPU pods, in community-cloud and secure-cloud tiers.

The two tiers run on different hosts and terms. Check which tier a pod is on before a long job.

Rent on RunPod

Vast.ai

billed per GPU-hour

Marketplace of host-listed GPUs; price and reliability vary by host.

Host quality varies. Filter for verified hosts and check the host's reliability before a long run.

Rent on Vast.ai

Referral links: RunLocalAI may earn a commission or account credits if you sign up and rent, at no extra cost to you. Hourly rates and which GPUs are listed change all the time, so check the provider's page before you start. Editorial opinions are independent of the referral relationship; see how we make money.

How to read these numbers

Measured here
Measured here - RunLocalAI ran this exact combo on owner hardware with public evidence.

Source-backed
Source-backed / community - a reproduced public source supports the speed, but it is not labeled as owner-measured.

Extrapolated
Extrapolated - predicted from a measured benchmark on similar-bandwidth hardware.

Estimated
Estimated - formula based on VRAM bandwidth and model architecture; not a benchmark row.

RunLocalAI Will-It-Run Framework →

Want a specific benchmark we don't have? Email Contact support and we'll prioritize it.