Posts: 63
Threads: 7
Joined: Sep 2026
Reputation:
0
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at small local stacks. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Posts: 32
Threads: 1
Joined: Sep 2026
Reputation:
0
A couple questions before I guess too hard. What model, what runtime, and roughly what context size?
I'm happy to test one more variant if you want a second data point.
Posts: 184
Threads: 23
Joined: Sep 2026
Reputation:
0
Quote:A couple questions before I guess too hard. What model, what runtime, and roughly what context size?
Good point. 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.
Mostly CUDA, sometimes wrong, usually measured
Posts: 44
Threads: 0
Joined: Sep 2026
Reputation:
0
Quote:Quote:A couple questions before I guess too hard. What model, what runtime, and roughly what context size?
What worked for me was pretty simple. If you're on SGLang, 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.
still benchmarking everything
Posts: 38
Threads: 4
Joined: Aug 2026
Reputation:
0
What worked for me was pretty simple. If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious.
curious and caffeinated