+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Inference Engines (https://www.datasculpting.ai/inference/forumdisplay.php?fid=9)
+--- Forum: Ollama / LM Studio / Desktop Runtimes (https://www.datasculpting.ai/inference/forumdisplay.php?fid=38)
+--- Thread: LM Studio surprisingly handy on M3 Max (/showthread.php?tid=1105)
LM Studio surprisingly handy on M3 Max - vectorcrate98 - 10-12-2026
Thought I'd post a small recipe because a lot of threads ask similar things.
Just sharing a setup that ended up working reasonably well: Kimi, vLLM, dual 3090, with a lot of attention on NVFP4.
Feel free to tear it apart if you see something dumb.
Re: LM Studio surprisingly handy on M3 Max - oxidestream - 10-13-2026
A couple things I'd check first. If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious.
Re: LM Studio surprisingly handy on M3 Max - edgeriver - 10-13-2026
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Llama and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
Re: LM Studio surprisingly handy on M3 Max - kernelgrid - 10-13-2026
I'd approach it in a boring order. If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Re: LM Studio surprisingly handy on M3 Max - mellowwire98 - 10-13-2026
Good point. I ended up in about the same place using SGLang.
Re: LM Studio surprisingly handy on M3 Max - promptspark58 - 10-14-2026
same here on my side.
Re: LM Studio surprisingly handy on M3 Max - dockridge - 10-14-2026
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at small local stacks.
Re: LM Studio surprisingly handy on M3 Max - mellowwire98 - 10-15-2026
Quote:My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at small local stacks.
subscribed, curious where this lands.