![]() |
|
industry move that matters for local users - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Miscellaneous Discussion (https://www.datasculpting.ai/inference/forumdisplay.php?fid=24) +--- Forum: News & Industry (https://www.datasculpting.ai/inference/forumdisplay.php?fid=26) +--- Thread: industry move that matters for local users (/showthread.php?tid=139) Pages:
1
2
|
Re: industry move that matters for local users - deepseeked - 09-09-2026 Interesting, I hadn't tried that. I don't think your conclusion is far off. Re: industry move that matters for local users - dockriver - 09-09-2026 Tried to reproduce it just now. On GB200 with MLX, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput collapsed. Re: industry move that matters for local users - audiopoint18 - 09-09-2026 same here on my side. Re: industry move that matters for local users - southpatch - 09-09-2026 What exact setup are you running? What model, what runtime, and roughly what context size? Re: industry move that matters for local users - amberrunner - 09-11-2026 Interesting, I hadn't tried that. I ended up in about the same place using LM Studio. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. There are a few different conversations hiding inside this thread, so being explicit about the goal helps. Re: industry move that matters for local users - deepseeked - 09-12-2026 What worked for me was pretty simple. If you're on MLX, I'd confirm the version first and then reduce variables until the behavior is obvious. |