Posts: 26
Threads: 3
Joined: Aug 2026
Reputation:
0
This keeps coming up in conversation so I figured I'd start a thread.
It feels like the conversation has shifted hard toward inference and serving details lately, and honestly that makes sense once you start dealing with router policy.
Curious whether that lines up with what other people are seeing.
I care more about stability than squeezing the last possible tokens/sec out of it.
Posts: 184
Threads: 23
Joined: Sep 2026
Reputation:
0
Thanks, that helps. 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: 52
Threads: 4
Joined: Sep 2026
Reputation:
0
I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Posts: 65
Threads: 5
Joined: Sep 2026
Reputation:
0
My first guess would be this: If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious.
Posts: 40
Threads: 4
Joined: Sep 2026
Reputation:
0
A couple questions before I guess too hard. What model, what runtime, and roughly what context size?
small models can still be good
Posts: 60
Threads: 5
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. I don't think your conclusion is far off. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Posts: 48
Threads: 4
Joined: Aug 2026
Reputation:
0
Good point. That matches what I saw on 4090. The biggest change for me was simplifying the stack instead of adding one more optimization layer. The logs were somehow calmer than I was.
Posts: 184
Threads: 23
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.
Mostly CUDA, sometimes wrong, usually measured
Posts: 31
Threads: 6
Joined: Sep 2026
Reputation:
0
I hit almost the same issue last night.
trying not to rebuild again
Posts: 30
Threads: 6
Joined: Sep 2026
Reputation:
0
Maybe, but I had the opposite result. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
learning in public