Posts: 45
Threads: 6
Joined: Aug 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 HBM constraints until they actually try to run this stuff for more than one afternoon.
Curious whether that lines up with what other people are seeing.
mostly local
Posts: 36
Threads: 5
Joined: Sep 2026
Reputation:
0
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
Posts: 30
Threads: 0
Joined: Sep 2026
Reputation:
0
Not sure I agree there. I've seen people blame prefill/decode split when the real issue was much more mundane. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
Posts: 41
Threads: 5
Joined: Aug 2026
Reputation:
0
Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.
Posts: 53
Threads: 7
Joined: Sep 2026
Reputation:
0
Appreciate the detail. I ended up in about the same place using TensorRT-LLM. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Posts: 41
Threads: 5
Joined: Aug 2026
Reputation:
0
I'd approach it in a boring order. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives. Once you know the plain path works, then add the faster path back in piece by piece.
Posts: 37
Threads: 4
Joined: Sep 2026
Reputation:
0
Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly.