+- 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: driver/framework news roundup (/showthread.php?tid=798)
Pages:
1
2
Re: driver/framework news roundup - phaseshed - 10-11-2026
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at router policy.
Re: driver/framework news roundup - deepseeked - 10-14-2026
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there.
Re: driver/framework news roundup - dockriver - 10-14-2026
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at VRAM headroom. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Re: driver/framework news roundup - deepseeked - 10-14-2026
Interesting, I hadn't tried that. I don't think your conclusion is far off.
Re: driver/framework news roundup - nanogarden - 10-15-2026
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher.
Re: driver/framework news roundup - phaseshed - 10-16-2026
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.