Skip to content

GPU × use-case guide · Vision-language

Is the A10G a good GPU for vision-language?

The A10G is a ampere NVIDIA GPU with 24 GB GDDR6 (600 GB/s), 35 TFLOPS BF16 / 35 TFLOPS FP8, and a 150 W TDP. Vision-language workloads care most about extra VRAM for the vision encoder and image tokens on top of the language model. Here's how the A10G measures up.

VRAM
24 GB
Bandwidth
600 GB/s
BF16
35 TFLOPS
Cheapest
$0.5/hr

What models fit on a single A10G?

Weights only, reserving ~25% of the 24 GB for KV cache, activations and fragmentation. ✓ = fits on one card.

ModelBF16FP8INT4
Llama 3.1 8B
Qwen 2.5 14B
Gemma 2 27B
Mixtral 8x7B (MoE)
Llama 3.3 70B
Qwen 2.5 72B
Llama 3.1 405B

Largest single-card fit: Llama 3.1 8B at BF16, Qwen 2.5 14B at FP8, Gemma 2 27B at INT4. Bigger models need tensor-parallel across 8 cards.

A10G for vision-language, specifically

Vision-language is context-heavy, so the KV cache — not the weights — is what fills the 24 GB. On the A10G you'll trade context length against batch size: long prompts mean fewer concurrent requests. Because it runs offline, batch aggressively to push tokens-per-dollar down. Size it precisely on the calculator.

A10G pricing across providers

ProviderOn-demand $/hrReserved $/hr
vast_ai$0.5
runpod$0.69
aws$1.21$0.75

Verdict

At 24 GB, the A10G is a value card best suited to smaller vision-language models (up to Gemma 2 27B with INT4 quantisation). For larger models you'll want more VRAM or multi-GPU.

See full A10Gspecs & pricing, size your model on the calculator, or compare every GPU on the GPU list.