
How are you running Llama 3.3 / 4 in Ollama. From 24GB cards up to Spark?
Trying to figure out where newer Llama models actually become practical in Ollama. ollama pull works on a small card; living with it daily doesn't.
Ollama tag sizes (Q4_K_M) — official library, not my benchmarks:
| Model | Ollama tag | On-disk (Q4_K_M) | Params | Source |
|---|---|---|---|---|
| Llama 3.3 70B | llama3.3:70b |
43 GB | 70.6B dense | Ollama |
| Llama 3.1 70B | llama3.1:70b |
43 GB | 70.6B dense | Ollama |
| Llama 4 Scout | llama4:16x17b |
67 GB | 109B total, 17B active (MoE) | Ollama |
| Llama 4 Maverick | llama4:128x17b |
245 GB | 402B total, 17B active (MoE) | Ollama |
| Llama 3.1 405B | llama3.1:405b |
243 GB | 406B dense | Ollama |
MoE gotcha (Llama 4): Scout has 109B weights on disk but only ~17B participate in each token's computation. You still need ~67 GB VRAM because Ollama loads all experts — the router can call any of them on the next token. Maverick is the same pattern at 245 GB. (Meta Llama 4 post). KV cache stacks on top, of course.
Hardware ladder — which tags fit where:
| Tier | VRAM | Example | 3.3 70B (43 GB) | 4 Scout (67 GB) | 4 Maverick (245 GB) |
|---|---|---|---|---|---|
| Consumer | 24 GB | RTX 4090 / 3090 | No — offload | No | No |
| Consumer | 32 GB | RTX 5090 | No | No | No |
| Workstation | 48 GB | RTX 6000 Ada | Tight | No | No |
| Multi-GPU | 96 GB | 3× RTX 5090 | Possible (split) | Tight / split | No |
| Unified | 128 GB | DGX Spark / GB10 | Comfortable | Fits | No — need ~245 GB+ |
I'm aiming for the 128 GB tier: first unified-memory class where llama3.3:70b (43 GB) is comfortable and llama4:16x17b / Scout (67 GB) actually fits, with headroom for context. Still not enough for Maverick (245 GB) or 405B (243 GB). Looking at DGX Spark / GB10, Mac Studio-class boxes, or renting hourly when I need a weekend on Scout rather than buying.
Anyone actually running Scout locally? Or still on 3.3 70B?
- 24–32 GB and living with offload / smaller models?
- 48 GB (6000 Ada) for 70B-class dense?
- 96 GB+ or 128 GB for Scout?
- Renting when you want Maverick / 405B-class sizes?
- Accepting the quantisation lower accuracy?
Especially curious if you're NOT on the box 24/7; does buying 128 GB hardware pencil out vs hourly rent?