+- 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: best local open-weight model this week: what are you seeing? (/showthread.php?tid=1099)
Pages:
1
2
Re: best local open-weight model this week: what are you seeing? - mintstation99 - 10-16-2026
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
I'm happy to test one more variant if you want a second data point.
Re: best local open-weight model this week: what are you seeing? - deltagrid - 10-16-2026
same here on my side.
Re: best local open-weight model this week: what are you seeing? - visionyard23 - 10-17-2026
Quote:same here on my side.
Thanks, that helps. I don't think your conclusion is far off. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
If you post your exact settings, people here can probably narrow it down pretty fast.
Re: best local open-weight model this week: what are you seeing? - sysstation69 - 10-17-2026
I think the bottleneck is somewhere else. I get why that seems right, but on dual 3090 the bottleneck felt elsewhere. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
I'm happy to test one more variant if you want a second data point.
Re: best local open-weight model this week: what are you seeing? - promptpoint - 10-17-2026
Good point. I ended up in about the same place using llama.cpp. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Re: best local open-weight model this week: what are you seeing? - batchyard - 10-17-2026
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with DeepSeek and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.