+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Miscellaneous Discussion (https://www.datasculpting.ai/inference/forumdisplay.php?fid=24)
+--- Forum: News & Industry (https://www.datasculpting.ai/inference/forumdisplay.php?fid=26)
+--- Thread: industry move that matters for local users for Llama (/showthread.php?tid=1397)
Pages:
1
2
industry move that matters for local users for Llama - audiopoint18 - 10-17-2026
Posting this in case it saves someone else a little time.
I'm helping a small team set up a local workflow. We don't need a giant stack, but we do care about prefill/decode split.
Would rather learn from your scars than collect my own all at once.
For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
Re: industry move that matters for local users for Llama - routearch - 10-18-2026
A couple things I'd check first. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time.
Re: industry move that matters for local users for Llama - vrampilot - 10-18-2026
Quote:A couple things I'd check first. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glam
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with DeepSeek and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Re: industry move that matters for local users for Llama - bytelab - 10-18-2026
That matches what I was seeing. The pattern around VRAM headroom 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.
Re: industry move that matters for local users for Llama - mangohouse - 10-18-2026
Need a little more detail here. Is this local-only or are you routing anything externally?
Re: industry move that matters for local users for Llama - southpatch - 10-18-2026
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at prefill/decode split. Not glamorous advice, but repeatable baselines save a lot of time.
Re: industry move that matters for local users for Llama - southpatch - 10-18-2026
Good point. That matches what I saw on B200. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Re: industry move that matters for local users for Llama - amberrunner - 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. Not glamorous advice, but repeatable baselines save a lot of time.
Re: industry move that matters for local users for Llama - bytestack - 10-19-2026
same here on my side.
Re: industry move that matters for local users for Llama - dockriver - 10-19-2026
I'd approach it in a boring order. 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.