+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: LLM Models (https://www.datasculpting.ai/inference/forumdisplay.php?fid=12)
+--- Forum: Open Weight (https://www.datasculpting.ai/inference/forumdisplay.php?fid=49)
+---- Forum: Hosted (https://www.datasculpting.ai/inference/forumdisplay.php?fid=50)
+---- Thread: high-context local setup (/showthread.php?tid=1304)
high-context local setup - latentgarden - 10-16-2026
This keeps coming up in conversation so I figured I'd start a thread.
The more I work with local setups, the more it seems like tail latency decides everything downstream.
Maybe obvious to some of you, but it clicked for me this week.
Re: high-context local setup - tensorriver - 10-16-2026
My first guess would be this: On 5090, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Re: high-context local setup - thetarunner - 10-16-2026
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at workstation thermals. Not glamorous advice, but repeatable baselines save a lot of time.
I'm happy to test one more variant if you want a second data point.
Re: high-context local setup - emberrunner - 10-16-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. Not glamorous advice, but repeatable baselines save a lot of time. I keep promising myself this is the last rebuild.
Re: high-context local setup - mangovault67 - 10-16-2026
Appreciate the detail. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Re: high-context local setup - dockriver - 10-16-2026
Quote:Appreciate the detail. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the
I hit almost the same issue last night.