+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Drivers / Frameworks / Toolkits (https://www.datasculpting.ai/inference/forumdisplay.php?fid=8)
+--- Forum: Apple / MLX (https://www.datasculpting.ai/inference/forumdisplay.php?fid=33)
+--- Thread: M3 Max for local use: early impressions (/showthread.php?tid=1088)
M3 Max for local use: early impressions - mlxgarden - 10-12-2026
Has anyone else run into this?
I'm mostly working with DeepSeek in PyTorch on dual 3090. The part I'm trying to understand is consumer GPUs.
If you've tested something similar, what did you keep and what did you stop bothering with?
Re: M3 Max for local use: early impressions - torchshed66 - 10-12-2026
Quote:Has anyone else run into this?
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.
Re: M3 Max for local use: early impressions - pixelcrate82 - 10-13-2026
Quote:Quote:Has anyone else run into this?
Did a small comparison this afternoon. On 4090 with llama.cpp, I saw basically the same behavior. The main thing that moved was latency, not quality.
Re: M3 Max for local use: early impressions - quietarch - 10-15-2026
Appreciate the detail. The pattern around INT4 has been pretty similar for me.
Re: M3 Max for local use: early impressions - bytesupply76 - 10-15-2026
My first guess would be this: If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.
Re: M3 Max for local use: early impressions - dockridge - 10-15-2026
I'd approach it in a boring order. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Re: M3 Max for local use: early impressions - plainember52 - 10-15-2026
Ran a quick check on my box. On B200 with MLX, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput collapsed.
Re: M3 Max for local use: early impressions - quietarch - 10-17-2026
same here on my side.
Re: M3 Max for local use: early impressions - turboarch95 - 10-17-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 quant drift. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.