SmolLM2 1.7B Instruct at FP16 needs 3.4 GB for its weights and 16.3 GB in total at 8K context with 8 concurrent users. That means it fits on a single A100 80GB SXM4. Every figure is computed by tokcalc's open-source capacity model.
| GPUs | Total VRAM | VRAM needed | Decode tok/s | Aggregate tok/s | TTFT | Cost / 1M tok | Fits? |
|---|---|---|---|---|---|---|---|
| 1× A100 | 80 GB | 16.3 GB | 382.4 | 4588 | 211.2 ms | $0.0726 | ✓ |
| 2× A100 | 160 GB | 16.3 GB | 650.0 | 15600 | 120.8 ms | $0.0427 | ✓ |
| 4× A100 | 320 GB | 16.3 GB | 1300 | 62400 | 75.4 ms | $0.0214 | ✓ |
| 8× A100 | 640 GB | 16.3 GB | 2600 | 249600 | 52.7 ms | $0.0107 | ✓ |
| Context | Concurrent users | KV per request | Fits? |
|---|---|---|---|
| 4K | 95 | 824.6 MB | ✓ fits |
| 8K | 47 | 1.61 GB | ✓ fits |
| 33K | 11 | 6.44 GB | ✓ fits |
| 66K | 5 | 12.88 GB | ✓ fits |
| 131K | 2 | 25.77 GB | ✓ fits |
| GPU | GPUs | Aggregate tok/s | Cost / 1M tok |
|---|---|---|---|
| RTX 3090 24GB | 1× | 2147 | $0.0323 |
| RTX 5090 32GB | 1× | 4111 | $0.0338 |
| RTX 4090 24GB | 1× | 2312 | $0.0480 |
| AMD MI300X 192GB | 1× | 12159 | $0.0571 |
| V100 SXM2 32GB | 1× | 2065 | $0.0673 |
| A100 40GB SXM4 | 1× | 3556 | $0.0703 |
Yes. SmolLM2 1.7B Instruct at FP16 needs 16.3 GB including the KV cache, and A100 80GB SXM4 has 80 GB — so it fits on a single GPU.
382.4 tokens/sec per stream and 4588 tok/s aggregate with continuous batching at 8 concurrent users. Time to first token is 211.2 ms, and inter-token latency is 2.6 ms.
$0.0726 per 1M output tokens at 1× A100 80GB SXM4 ($1.20/hr). That is the marginal hardware cost — add idle capacity, ops, and egress for the real figure.
3.4 GB for the weights at FP16, plus 12.9 GB of KV cache for 8 concurrent requests at 8K context — 16.3 GB total. Every extra concurrent user at long context costs more, so leave headroom.
It works. Compare $0.0726 per 1M tokens against the alternatives below — the cheapest option that fits the same workload is 2× RTX 3080 10GB at $0.0187, and the fastest is 1× Cerebras CS-3 (WSE-3) at 45882 tok/s.
Same formulas, your context length, concurrency, and quantisation.