Posts: 41
Threads: 5
Joined: Aug 2026
Reputation:
0
Spent some time on this today and wanted to compare notes.
I'm comparing two approaches here: keep it simple on B200, or squeeze more out of the stack and deal with the complexity.
What would you pick if you had to live with it for a few months?
Posts: 54
Threads: 5
Joined: Aug 2026
Reputation:
0
I'd approach it in a boring order. If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time.
Posts: 82
Threads: 7
Joined: Sep 2026
Reputation:
0
Appreciate the detail. I ended up in about the same place using SGLang. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Posts: 49
Threads: 6
Joined: Sep 2026
Reputation:
0
Tried to reproduce it just now. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.
Posts: 82
Threads: 7
Joined: Sep 2026
Reputation:
0
I'd start with the simpler stack.
Posts: 41
Threads: 6
Joined: Oct 2026
Reputation:
0
A couple questions before I guess too hard. Do you see the same thing with a smaller batch or shorter prompt?
Posts: 121
Threads: 15
Joined: Sep 2026
Reputation:
0
What exact setup are you running? Are you testing this on GB200 or something else?
image models by night, local pipelines by day