+- 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: Local (https://www.datasculpting.ai/inference/forumdisplay.php?fid=51)
+---- Thread: recipes for a good local stack (/showthread.php?tid=285)
Pages:
1
2
Re: recipes for a good local stack - mlxgarden - 09-21-2026
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.
Re: recipes for a good local stack - rocmcrate26 - 09-21-2026
Quote:Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at long context. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Re: recipes for a good local stack - rasterbench - 09-21-2026
Thanks, that helps. I ended up in about the same place using llama.cpp.
Re: recipes for a good local stack - relayforge - 09-21-2026
I tested this tonight. On M3 Max with llama.cpp, I saw basically the same behavior.
Re: recipes for a good local stack - mlxgarden - 09-22-2026
I don't think that's the whole story. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. At this point the real bottleneck is my patience.
Re: recipes for a good local stack - mangoquill - 09-22-2026
worth checking the driver first.