For RAG specifically, prefill speed matters more than decode and why Strix Halo struggles for interactive use
Mirrored from r/LocalLLaMA for archival readability. Support the source by reading on the original site.
| Seeing a lot of "what hardware for local RAG" threads lately, and the framing that keeps getting missed is: decode tok/s is not the bottleneck for RAG. Prefill is the bottleneck for RAG. RAG queries stuff thousands of tokens of retrieved context into every prompt. On unified memory boxes like Strix Halo, prefill throughput lags way behind a discrete GPU even though decode speed on MoE models is perfectly fine (25-40 tok/s). A single 24GB discrete card chews through the same context in a few seconds; unified memory setups can leave you staring at a 20-60 second pause before the first token comes back. If your work is more batch style you're more than fine. but if its constantly tweqking you need something else Practical takeaway if you're budget constrained: pick a board with a free PCIe slot so you can drop in a discrete card later just to offload prefill, rather than assuming unified memory alone will feel good for interactive RAG. [link] [comments] |
More from r/LocalLLaMA
-
Unpopular opinion Qwen 3.8 is hard to understand
Aug 30
-
Qwen3.8-Flash-Next turns 4xR9700 into a local AI powerhouse! 120 t/s TG and 12k t/s PP single request with optimized vLLM
Aug 30
-
Oh so that's where my PCIe lanes went...
Aug 30
-
Uncensored Multi-Model Releases, LongCat-Flash-Lite-Sparse with MTPs and LSAs, Qwen3.8-27B with MTPs, Qwen3.5-122B-A10B with MTPs, Qwen3-Coder-Next and Laguna-S2.1 with Vision, All Available in GGUF Format! Bonus: Links to my llama.cpp Fork for LongCat-Flash-Lite Support and…
Aug 30
Discussion (0)
Sign in to join the discussion. Free account, 30 seconds — email code or GitHub.
Sign in →No comments yet. Sign in and be the first to say something.