Posts: 63
Threads: 13
Joined: Sep 2026
Reputation:
0
Posting this in case it saves someone else a little time.
If you were starting from scratch today for this use case, what would you choose first and what would you ignore?
I'm especially interested in mistakes worth avoiding.
I care more about stability than squeezing the last possible tokens/sec out of it.
Posts: 28
Threads: 3
Joined: Aug 2026
Reputation:
0
A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at continuous batching. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Posts: 23
Threads: 1
Joined: Sep 2026
Reputation:
0
My first guess would be this: 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.
Posts: 40
Threads: 2
Joined: Sep 2026
Reputation:
0
My first guess would be this: On B200, 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.
Posts: 37
Threads: 1
Joined: Oct 2026
Reputation:
0
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.
If you post your exact settings, people here can probably narrow it down pretty fast.
Posts: 33
Threads: 4
Joined: Aug 2026
Reputation:
0
worth checking the driver first.
Posts: 44
Threads: 3
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 tail latency. Not glamorous advice, but repeatable baselines save a lot of time.
Posts: 341
Threads: 51
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.
measure twice, benchmark three times
Posts: 27
Threads: 2
Joined: Sep 2026
Reputation:
0
I think the bottleneck is somewhere else. I've seen people blame speculative decoding when the real issue was much more mundane. Worth testing the simpler explanation before adopting the more interesting one.
team red, team patient
Posts: 142
Threads: 20
Joined: Sep 2026
Reputation:
0
I'd start with the simpler stack.
small models can still be useful