GLM-5.3 (MoE) at AWQ 4-bit needs 414.3 GB for its weights and 420.2 GB in total at 8K context with 8 concurrent users. That means it needs 8× 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 | 420.2 GB | 0.000 | 0.000 | — | — | ✗ |
| 2× A100 | 160 GB | 420.2 GB | 0.000 | 0.000 | — | — | ✗ |
| 4× A100 | 320 GB | 420.2 GB | 0.000 | 0.000 | — | — | ✗ |
| 8× A100 | 640 GB | 420.2 GB | 739.9 | 71027 | 282.3 ms | $0.0375 | ✓ |
| Context | Concurrent users | KV per request | Fits? |
|---|---|---|---|
| 4K | 613 | 15.70 GB | ✓ fits |
| 8K | 306 | 31.41 GB | ✓ fits |
| 33K | 76 | 125.63 GB | ✓ fits |
| 66K | 38 | 251.26 GB | ✓ fits |
| 131K | 19 | 502.51 GB | ✓ fits |
| GPU | GPUs | Aggregate tok/s | Cost / 1M tok |
|---|---|---|---|
| H100 SXM5 80GB | 8× | 118970 | $0.0467 |
| B200 SXM 192GB | 4× | 71027 | $0.0939 |
| H200 SXM5 141GB | 4× | 42616 | $0.1043 |
Yes, but it needs 8× A100 80GB SXM4. At AWQ 4-bit the total footprint is 420.2 GB (414.3 GB of weights plus 5.9 GB of KV cache at 8K × 8 concurrent users), against 640 GB of available VRAM across 8 GPUs.
739.9 tokens/sec per stream and 71027 tok/s aggregate with continuous batching at 8 concurrent users. Time to first token is 282.3 ms, and inter-token latency is 1.4 ms.
$0.0375 per 1M output tokens at 8× A100 80GB SXM4 ($1.20/hr). That is the marginal hardware cost — add idle capacity, ops, and egress for the real figure.
414.3 GB for the weights at AWQ 4-bit, plus 5.9 GB of KV cache for 8 concurrent requests at 8K context — 420.2 GB total. Every extra concurrent user at long context costs more, so leave headroom.
It works. Compare $0.0375 per 1M tokens against the alternatives below — the cheapest option that fits the same workload is 8× A100 80GB SXM4 at $0.0375, and the fastest is 8× H100 SXM5 80GB at 118970 tok/s.
Same formulas, your context length, concurrency, and quantisation.