Inference
70B still worth the pain - Printable Version

+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: LLM Models (https://www.datasculpting.ai/inference/forumdisplay.php?fid=12)
+--- Forum: Proprietary / Frontier (https://www.datasculpting.ai/inference/forumdisplay.php?fid=48)
+--- Thread: 70B still worth the pain (/showthread.php?tid=1459)

Pages: 1 2


Re: 70B still worth the pain - fusedhall - 10-18-2026

Thanks, that helps. I ended up in about the same place using TensorRT-LLM. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.


Re: 70B still worth the pain - llmtrack26 - 10-18-2026

Quote:Thanks, that helps. I ended up in about the same place using TensorRT-LLM. Worth rechecking your defaults though, because one bad assumption can make

Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly. I expected the model choice to matter more than it did.


Re: 70B still worth the pain - nanopatch - 10-18-2026

That matches what I was seeing. I don't think your conclusion is far off.


Re: 70B still worth the pain - relaynest82 - 10-18-2026

Interesting, I hadn't tried that. The pattern around batch size has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.


Re: 70B still worth the pain - labnest - 10-18-2026

What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at MoE serving. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.


Re: 70B still worth the pain - macrotinker - 10-19-2026

My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at prefix caching. Not glamorous advice, but repeatable baselines save a lot of time.


Re: 70B still worth the pain - paperrunner - 10-19-2026

Appreciate the detail. The pattern around HBM constraints has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.


70B still worth the pain - dockkite69 - 10-19-2026

Did a bit of testing and thought I'd post the result here.

I tried this with Mixtral using LM Studio on Threadripper box. The headline result was better than I expected, but VRAM headroom still ended up being the limiting factor.

Nothing scientific here, just practical notes from a real setup.


Re: 70B still worth the pain - dockworks23 - 10-19-2026

What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.


Re: 70B still worth the pain - latentscope35 - 10-19-2026

following this because I'm in the same boat.