Posts: 38
Threads: 9
Joined: Sep 2026
Reputation:
0
Spent some time on this today and wanted to compare notes.
I'm comparing two approaches here: keep it simple on mini PC, or squeeze more out of the stack and deal with the complexity.
Trying to avoid rebuilding the whole thing twice.
curious and caffeinated
Posts: 63
Threads: 4
Joined: Sep 2026
Reputation:
0
Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly.
Posts: 54
Threads: 3
Joined: Sep 2026
Reputation:
0
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.
Posts: 23
Threads: 3
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. I ended up in about the same place using SGLang. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Posts: 211
Threads: 21
Joined: Sep 2026
Reputation:
0
I'd start with the simpler stack.
7900 XTX / ROCm / somehow still optimistic
Posts: 82
Threads: 7
Joined: Sep 2026
Reputation:
0
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at long context. Not glamorous advice, but repeatable baselines save a lot of time.
Posts: 69
Threads: 3
Joined: Sep 2026
Reputation:
0
I'd approach it in a boring order. On 4090, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time.
still benchmarking everything
Posts: 50
Threads: 6
Joined: Sep 2026
Reputation:
0
Did a small comparison this afternoon. I couldn't reproduce the slowdown until I pushed context much higher. I expected the model choice to matter more than it did.
Posts: 25
Threads: 3
Joined: Sep 2026
Reputation:
0
Thanks, that helps. I don't think your conclusion is far off.
Posts: 76
Threads: 8
Joined: Aug 2026
Reputation:
0
I hit almost the same issue last night.
learning in public