![]() |
|
tools worth paying for on 5090 - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Apps / Utilities / Tools (https://www.datasculpting.ai/inference/forumdisplay.php?fid=18) +--- Forum: Online / Hosted (https://www.datasculpting.ai/inference/forumdisplay.php?fid=19) +--- Thread: tools worth paying for on 5090 (/showthread.php?tid=1063) Pages:
1
2
|
tools worth paying for on 5090 - emberrunner - 10-11-2026 Curious what people here are seeing. I'm mostly working with Mistral in MLX on A6000. The part I'm trying to understand is router policy. Would appreciate practical advice rather than theory. Re: tools worth paying for on 5090 - southpatch - 10-12-2026 Quote:Curious what people here are seeing. A couple things I'd check first. If you're on LM Studio, 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: tools worth paying for on 5090 - torchsmith25 - 10-12-2026 Quote:Quote:Curious what people here are seeing. Need a little more detail here. Are you testing this on A6000 or something else? Re: tools worth paying for on 5090 - promptfield - 10-12-2026 same here on my side. Re: tools worth paying for on 5090 - vramarch - 10-12-2026 My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at continuous batching. Once you know the plain path works, then add the faster path back in piece by piece. Re: tools worth paying for on 5090 - thetashed24 - 10-12-2026 subscribed, curious where this lands. Re: tools worth paying for on 5090 - macrostack69 - 10-13-2026 Appreciate the detail. The pattern around NVFP4 has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. Re: tools worth paying for on 5090 - bytelab - 10-14-2026 What worked for me was pretty simple. If you're on llama.cpp, 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: tools worth paying for on 5090 - southpatch - 10-15-2026 My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. Re: tools worth paying for on 5090 - tensorriver - 10-15-2026 that fixed it for me too. |