RAG and RL tool calling are quietly driving CPU demand back into ML training
TheZachMueller · x · 2026-10-01
Stas Bekman highlights a shift in ML resource patterns: CPUs were once only for DataLoader work, but RAG retrieval and RL tool calling now require significant CPU again. He updated his use-case docs and asked for other unexpected CPU uses.
TheZachMueller adds that sandboxing — running agent code execution environments — may be the biggest new CPU consumer of all. The thread suggests agent-driven training pipelines are upending GPU/CPU capacity planning assumptions.
Related event: RAG and RL tool calls put CPUs back in ML training(3 posts)→
More from Infra
- Mobile AI Factory: agents auto-build on-device SLMs with 19x less GPU time — pmttyji · 2026-11-16
- Stratechery's Fictional Obituary: Imagining Jensen Huang's 2026 Exit From Nvidia — Gregory_C_Allen · 2026-11-16
- vLLM serves DeepSeek V4.1-Flash at 954K tokens/s per GPU, $38.96/GPU-hour on GB300 NVL72 — bookwormengr · 2026-11-16
- Colossus 2's 1.2M B200s could generate ~$400B/year in tokens at DeepSeek Flash rates — bookwormengr · 2026-11-16
- BIS issues rule blocking remote access to US AI chips via third-country data centers — teortaxesTex · 2026-11-16
- Qdrant 1.20.1: 50% fewer cold-storage reads, ~2x faster quantization, agent-ready setup — qdrant_engine · 2026-11-16