Posts: 37
Threads: 2
Joined: Aug 2026
Reputation:
0
Has anyone else run into this?
I'm trying to decide whether to keep the current stack or change course. Main question is how people here are handling batch size.
If you've tested something similar, what did you keep and what did you stop bothering with?
Posts: 31
Threads: 2
Joined: Sep 2026
Reputation:
0
Can you fill in a bit more context? Are you testing this on B200 or something else?
Posts: 41
Threads: 5
Joined: Aug 2026
Reputation:
0
I tested this tonight. My result was mixed: first run looked bad, second run looked normal. I expected the model choice to matter more than it did.
There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Posts: 36
Threads: 5
Joined: Sep 2026
Reputation:
0
following this because I'm in the same boat.
Posts: 39
Threads: 5
Joined: Sep 2026
Reputation:
0
I don't think that's the whole story. I've seen people blame reranking 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: 31
Threads: 2
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. That matches what I saw on Threadripper box.
Posts: 68
Threads: 9
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious.
Posts: 27
Threads: 1
Joined: Aug 2026
Reputation:
0
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there.
Posts: 128
Threads: 12
Joined: Sep 2026
Reputation:
0
I hit almost the same issue last night.
rack in the garage • local models everywhere
Posts: 54
Threads: 5
Joined: Aug 2026
Reputation:
0
Interesting, I hadn't tried that. 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.