Posts: 42
Threads: 4
Joined: Oct 2026
Reputation:
0
This keeps coming up in conversation so I figured I'd start a thread.
One thing I keep noticing is that people underestimate tail latency until they actually try to run this stuff for more than one afternoon.
Curious whether that lines up with what other people are seeing.
curious and caffeinated
Posts: 33
Threads: 2
Joined: Sep 2026
Reputation:
0
Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Worth testing the simpler explanation before adopting the more interesting one.
Posts: 47
Threads: 6
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Posts: 33
Threads: 0
Joined: Aug 2026
Reputation:
0
What exact setup are you running? Do you see the same thing with a smaller batch or shorter prompt?
I'm happy to test one more variant if you want a second data point.
Posts: 57
Threads: 8
Joined: Oct 2026
Reputation:
0
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at small local stacks. Once you know the plain path works, then add the faster path back in piece by piece.
If you post your exact settings, people here can probably narrow it down pretty fast.
Posts: 45
Threads: 3
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
Posts: 53
Threads: 4
Joined: Sep 2026
Reputation:
0
Good point. That matches what I saw on A6000.
Posts: 142
Threads: 20
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 useful
Posts: 68
Threads: 3
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.
Posts: 42
Threads: 4
Joined: Oct 2026
Reputation:
0
My first guess would be this: If you're on TensorRT-LLM, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.
curious and caffeinated