![]() |
|
frankenmerges anyone kept using with MLX - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Harnesses, Agents & Orchestration (https://www.datasculpting.ai/inference/forumdisplay.php?fid=11) +--- Forum: MCP / APIs / Tool Calling (https://www.datasculpting.ai/inference/forumdisplay.php?fid=46) +--- Thread: frankenmerges anyone kept using with MLX (/showthread.php?tid=762) |
frankenmerges anyone kept using with MLX - rocmpath - 10-04-2026 Posting this in case it saves someone else a little time. If you were starting from scratch today for this use case, what would you choose first and what would you ignore? Simple and boring is a valid answer. Re: frankenmerges anyone kept using with MLX - southtinker - 10-05-2026 Quote:Posting this in case it saves someone else a little time. Good point. I don't think your conclusion is far off. The biggest change for me was simplifying the stack instead of adding one more optimization layer. Re: frankenmerges anyone kept using with MLX - localtinker - 10-05-2026 What worked for me was pretty simple. If you're on LM Studio, 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: frankenmerges anyone kept using with MLX - rasterbench - 10-06-2026 that fixed it for me too. I keep promising myself this is the last rebuild. Re: frankenmerges anyone kept using with MLX - labline - 10-07-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. Not glamorous advice, but repeatable baselines save a lot of time. Re: frankenmerges anyone kept using with MLX - deepseeked - 10-08-2026 Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal. Re: frankenmerges anyone kept using with MLX - cozyarch - 10-11-2026 subscribed, curious where this lands. |