TextDense7.24B params33K max context

Mistral 7B v0.3 VRAM Requirements: How Many GPUs & What It Costs

Mistral 7B v0.3 needs 14.5 GB of VRAM for its weights at FP16 — 15.0 GB once a KV cache is loaded. Below is the full breakdown: which GPUs fit, how many you need, what it serves, and what it costs per million tokens. Every figure comes from tokcalc's open-source capacity model.

Weights (FP16)
14.5 GB
15.0 GB with KV cache
Fits on 1 GPU?
Yes
A10G 24GB or larger
Cheapest config
$0.0399
4× RTX 3080 10GB / 1M tokens
Fastest config
10773
tok/s on 1× Cerebras CS-3 (WSE-3)
VRAM requirement by quantization
Weight footprint = params × bytes per param. The “with KV cache” column adds one request at 4K context.
QuantizationWeightsWith KV cacheSmallest single GPU
FP16recommended14.5 GB15.0 GBT4 16GB (16 GB)
FP8 (E4M3)7.2 GB7.8 GBRTX 3080 10GB (10 GB)
AWQ 4-bit4.0 GB4.5 GBRTX 3080 10GB (10 GB)
Which GPU should you use?
Reference workload: 8K context, 8 concurrent users, continuous batching, FP16. Ranked by fitting first, then by tokens per dollar-hour.
GPUGPUsTotal VRAMDecode tok/sAggregate tok/sCost / 1M tokens
RTX 3080 10GB4×40 GB116.05568$0.0399
RTX 4080 16GB2×32 GB54.721313$0.1269
RTX 3090 24GB1×24 GB42.02504.2$0.1377
RTX 5090 32GB1×32 GB80.44965.3$0.1439
T4 16GB2×32 GB24.42586.1$0.1896
RTX A4000 16GB2×32 GB34.19820.5$0.2031
RTX 4090 24GB1×24 GB45.25543.0$0.2046
AMD MI300X 192GB1×192 GB237.92855$0.2432
V100 SXM2 32GB1×32 GB40.40484.8$0.2865
A100 40GB SXM41×40 GB69.58834.9$0.2994
AMD MI325X 288GB1×288 GB269.33232$0.3008
A100 80GB SXM41×80 GB89.781077$0.3094

RTX 3080 10GB has no NVLink, so 4-way tensor parallelism runs over PCIe. tokcalc applies a flat 0.85× multi-GPU efficiency factor for this, which is realistic for NVLink-equipped datacenter cards but optimistic for PCIe scale-out — treat the throughput and cost figures for this configuration as an upper bound, and measure before committing.

How concurrency changes with context length
On 4× RTX 3080 10GB at FP16. KV cache scales linearly with context, so long contexts cut the number of users you can serve from the same GPUs.
ContextConcurrent usersKV per requestFits?
4K47549.8 MB✓ fits
8K231.07 GB✓ fits
33K54.29 GB✓ fits
66K28.59 GB✓ fits
131K117.18 GB✓ fits
Frequently asked questions

Can Mistral 7B v0.3 run on a single GPU?

Yes. At FP16 the model needs 15.0 GB of VRAM, so it fits on a single A10G 24GB or anything with more VRAM. At full FP16 it needs 15.0 GB, which fits on one T4 16GB or larger.

How many GPUs does Mistral 7B v0.3 need?

At FP16 with 8,192-token context and 8 concurrent users, the cheapest configuration that fits is 4× RTX 3080 10GB (40 GB total VRAM). $0.0399 per 1M output tokens.

How fast can Mistral 7B v0.3 be served?

On 1× Cerebras CS-3 (WSE-3) at FP16, the aggregate throughput is 10773 tokens/sec with continuous batching. That hardware has no published rental price, so its cost per million tokens is not comparable.

How much VRAM does Mistral 7B v0.3 need?

Weights alone: 14.5 GB at FP16, 14.5 GB at FP16. Add KV cache for your context length and concurrency — every concurrent request at 8,192 tokens costs extra VRAM, so budget headroom above the weight figure.

Is it cheaper to self-host Mistral 7B v0.3 than to call an API?

At 4× RTX 3080 10GB the marginal cost is $0.0399 per 1M output tokens, before you add idle capacity, ops staff, or egress. That is typically cheaper than frontier API pricing at sustained volume, but API calls win when your load is bursty or too small to keep a GPU busy. The Build vs Buy tab on tokcalc prices this against a specific provider for you.

Try Mistral 7B v0.3 with your own context and concurrency

The calculator uses the exact same formulas as this page — change the workload and watch every number update.

Open in calculator
Model architecture
The numbers behind the KV-cache and throughput math.
Total parameters7.24B
Active parameters per token7.24B
ArchitectureDense
Attention layoutFull attention (GQA)
Transformer layers32
Hidden dimension4096
Attention heads32 query / 8 KV (GQA)
Head dimension128
Vocabulary size32,768
Max context (catalog)33K
KV cache per token @ 8K128.0 KB

Every layer caches keys and values for the whole context, so the KV cache grows linearly with conversation length.