+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Optimization & Performance (https://www.datasculpting.ai/inference/forumdisplay.php?fid=10)
+--- Forum: Quantization (https://www.datasculpting.ai/inference/forumdisplay.php?fid=40)
+--- Thread: quant choices for 70B local (/showthread.php?tid=1008)
Pages:
1
2
Re: quant choices for 70B local - homelabhenry - 10-18-2026
What worked for me was pretty simple. On 5090, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Re: quant choices for 70B local - turboscope - 10-18-2026
Interesting, I hadn't tried that. The pattern around tokens/sec has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing. The logs were somehow calmer than I was.
Re: quant choices for 70B local - cacheworks - 10-18-2026
Thanks, that helps. I ended up in about the same place using PyTorch. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Re: quant choices for 70B local - relaynest82 - 10-18-2026
Did a small comparison this afternoon. On M3 Max with llama.cpp, I saw basically the same behavior. The main thing that moved was latency, not quality.
Re: quant choices for 70B local - cacheworks - 10-19-2026
I think the bottleneck is somewhere else. I've seen people blame VRAM headroom when the real issue was much more mundane. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Re: quant choices for 70B local - vrambandit - 10-19-2026
Interesting, I hadn't tried that. That matches what I saw on dual 3090. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.