What runs this LLM?

Pick the model you want to serve. We size it from the released checkpoint and list the cheapest configurations you can rent today that hold it β€” with the on-demand and serverless rate for each.

1 Β· Choose a model

Model
Precision
Context

2 Β· What it needs

Qwen3 8B at 16-bit

20 GB of VRAM

at short context β€” measured from the released checkpoint, not estimated from parameter count.

Model weights
16 GB
KV cachefolded into overhead
β€”
Runtime overhead20% of weights
3.3 GB

About this model

Qwen3 8BAlibaba
Parameters
8.2B
Released at
16-bit
Measured weights
16 GB
Source checkpointQwen/Qwen3-8B

3 Β· Where to run it

Bookable configurations

Cheapest first, checked against 101 GPU types with live bookable capacity.

ConfigurationTotal VRAMOn-demandServerlessGPU details
2Γ— NVIDIA Tesla V100 16GB
32 GB
12 GB free
$0.06/hr
$0.03/GPU-hr
Vast.ai logoVast.ai
β€”See all prices
2Γ— NVIDIA RTX A2000
24 GB
4.3 GB free
$0.06/hr
$0.03/GPU-hr
Vast.ai logoVast.ai
β€”See all prices
1Γ— NVIDIA RTX 3090
24 GB
4.3 GB free
$0.10/hr
Vast.ai logoVast.ai
$0.69/hr
Runpod logoRunpod
See all prices
1Γ— NVIDIA RTX A4500
20 GB
0.3 GB free
$0.11/hr
Vast.ai logoVast.ai
$0.58/hr
Runpod logoRunpod
See all prices
2Γ— NVIDIA RTX 3060
24 GB
4.3 GB free
$0.12/hr
$0.06/GPU-hr
Vast.ai logoVast.ai
β€”See all prices
2Γ— NVIDIA Titan Xp
24 GB
4.3 GB free
$0.12/hr
$0.06/GPU-hr
Vast.ai logoVast.ai
β€”See all prices
2Γ— NVIDIA GTX 1080 Ti
22 GB
2.3 GB free
$0.12/hr
$0.06/GPU-hr
Vast.ai logoVast.ai
β€”See all prices
1Γ— NVIDIA RTX 4090
24 GB
4.3 GB free
$0.13/hr
Vast.ai logoVast.ai
$1.10/hr
Runpod logoRunpod
See all prices

Showing the 8 cheapest. Model weights plus 20% for runtime overhead, from measured checkpoint sizes; a stated context length adds its KV cache on top. Each price is the cheapest bookable rate for that exact instance size, for the whole configuration β€” the cheaper of the two is highlighted and orders the table. A Γ—N figure is total VRAM across N cards and makes no claim about interconnect throughput.

How this is worked out

Weight sizes are measured from the actual checkpoint files on Hugging Face β€” never derived from parameter count, which gets quantized releases wrong. On top of the weights we assume 20% for activations, CUDA context and allocator slack. Stating a context length adds its KV cache explicitly, computed only for architectures whose cache shape the config states unambiguously.

A configuration that holds the weights and cache but not that full margin is marked as a tight fit rather than hidden β€” it will load, and may well run at batch size one, but expect trouble under load.

Prices are the cheapest bookable rate for that exact instance size, refreshed with the rest of the catalog.

Keep looking