![]() |
|
which local open model do you keep coming back to: what are you seeing? - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: LLM Models (https://www.datasculpting.ai/inference/forumdisplay.php?fid=12) +--- Forum: Open Weight (https://www.datasculpting.ai/inference/forumdisplay.php?fid=49) +---- Forum: Hosted (https://www.datasculpting.ai/inference/forumdisplay.php?fid=50) +---- Thread: which local open model do you keep coming back to: what are you seeing? (/showthread.php?tid=224) Pages:
1
2
|
Re: which local open model do you keep coming back to: what are you seeing? - deepseeked - 09-13-2026 Quote:What worked for me was pretty simple. If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious. Once Good point. I don't think your conclusion is far off. Re: which local open model do you keep coming back to: what are you seeing? - batchshed - 09-14-2026 Quote:[quote]What worked for me was pretty simple. If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obviou My first guess would be this: If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious. Re: which local open model do you keep coming back to: what are you seeing? - cachebench - 09-14-2026 A couple things I'd check first. If you're on TensorRT-LLM, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time. Re: which local open model do you keep coming back to: what are you seeing? - labnest - 09-17-2026 Maybe, but I had the opposite result. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Could be a workload difference, but I wouldn't generalize too fast from one setup. |