GPU Pricing in 2026: How to Pick the Right Instance for ML Inference
T4, L4, A10G, A100, H100 — a practical guide to choosing the right GPU.
GPU Pricing in 2026: How to Pick the Right Instance for ML Inference
GPU pricing has never been more fragmented. Between hyperscalers, specialized GPU clouds, and the NVIDIA shortage, picking the right instance for inference is genuinely hard. Here's a practical framework.
The GPU Landscape (August 2026)
| GPU | VRAM | Best For | AWS Price/hr | GCP Price/hr | RunPod Price/hr |
|---|---|---|---|---|---|
| T4 | 16GB | Light inference, batch < 100 tokens | $0.35 | $0.28 | $0.29 |
| L4 | 24GB | Medium LLMs (7B), SDXL | $0.50 | $0.42 | $0.44 |
| A10G | 24GB | Production LLMs (13B) | $0.75 | $0.69 | $0.59 |
| A100-40G | 40GB | Large LLMs (70B quantized) | $1.90 | $1.55 | $1.29 |
| H100 | 80GB | Frontier models (405B+) | $2.90 | $2.45 | Not available |
The Decision Framework
1. Start with VRAM, Not Speed
A surprising number of inference failures are OOM errors — not slow responses. Your model weights + KV cache + overhead must fit in VRAM.
Rule of thumb:
Required VRAM = (Model size in GB * 1.25) + (batch_size * avg_sequence_length * 2 * hidden_dim / 1e9)
For a 7B parameter model (14GB in FP16):
- VRAM need: 14 * 1.25 = 17.5GB
- Minimum instance: L4 (24GB) or higher
For a 13B model (26GB in FP16):
- VRAM need: 26 * 1.25 = 32.5GB
- Minimum instance: A100-40G
2. Don't Pay for Idle GPUs
The biggest cost lever is utilization. A T4 instance at 100% utilization is cheaper than an A100 at 20%.
Serverless vs Reserved vs Spot:
| Pricing Model | Discount | Best For |
|---|---|---|
| On-demand | 0% (baseline) | Bursty, unpredictable traffic |
| Reserved (1yr) | 30-40% off | Stable, 24/7 workloads |
| Spot/Preemptible | 60-80% off | Batch inference, non-critical workloads |
| Serverless (pay-per-request) | Varies | Low/medium traffic, < 10 QPS |
Recommendation: Mix and match. Use reserved for baseline traffic, serverless for bursts, spot for batch jobs.
3. The Cloud Multiplier
Raw GPU cost isn't the full picture. You're also paying for:
- Instance overhead: vCPUs, RAM, networking (included in the hourly rate)
- Storage: Container images, model artifacts (ECR/S3/Blob)
- Data transfer: Ingress is usually free, egress is $0.05-0.12/GB
- Monitoring: CloudWatch, Azure Monitor, Cloud Logging
- Management overhead: Your team's time configuring and maintaining
The "all-in" cost is typically 1.3-1.5x the raw GPU price.
4. Geographic Arbitrage
GPU prices vary by region:
| Region | T4 Price | Notes |
|---|---|---|
| us-east-1 | $0.35/hr | Baseline |
| us-west-2 | $0.37/hr | Slightly higher |
| eu-west-1 | $0.39/hr | GDPR compliance needed |
| ap-southeast-1 | $0.42/hr | Higher latency from US |
| ap-northeast-1 | $0.33/hr | Sometimes cheaper than us-east-1 |
Deploying to ap-northeast-1 instead of us-east-1 saves 6% on GPU costs. With Roptal's multi-cloud orchestration, you can shift workloads based on regional pricing without re-platforming.
The RunPod Question
RunPod's GPU cloud deserves special attention. Their "community cloud" (peer-to-peer GPU rental) consistently undercuts hyperscalers by 20-40%:
- T4: $0.24/hr (community) vs $0.29/hr (secure cloud)
- A100-80G: $1.10/hr (community) vs $1.59/hr (secure cloud)
The tradeoff: community GPUs can be reclaimed with 1 minute notice. Perfect for batch processing, risky for production APIs.
Practical Recommendations
Small inference (< 100 QPS, 7B model):
- Use a single L4 instance ($350/month reserved)
- Add a second L4 for redundancy if uptime is critical
Medium inference (100-1000 QPS, 13B model):
- Base: 2x A10G reserved ($1,100/month)
- Peak: 2x A10G spot for surges ($200/month variable)
- Total: ~$1,300/month
High throughput (1000+ QPS, LLM serving):
- Base: 4x A100-40G reserved ($4,400/month)
- Burst: 2x A100-40G spot ($400/month)
- Consider vLLM/TensorRT-LLM for 2-5x throughput improvement
- Total: ~$4,800/month
The Multi-Cloud Advantage
The cheapest GPU today might be the most expensive tomorrow. NVIDIA allocations shift, cloud providers adjust pricing, and spot instance availability fluctuates by the minute.
The real win: being able to run on any cloud. Deploy once, switch providers based on real-time pricing. That's the bet Roptal is making — and it's why we built multi-cloud orchestration into the platform from day one.