Posts: 52
Threads: 4
Joined: Sep 2026
Reputation:
0
I don't think that's the whole story. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Worth testing the simpler explanation before adopting the more interesting one.
Posts: 24
Threads: 1
Joined: Sep 2026
Reputation:
0
A couple questions before I guess too hard. Do you see the same thing with a smaller batch or shorter prompt?
learning in public
Posts: 63
Threads: 1
Joined: Sep 2026
Reputation:
0
Tried to reproduce it just now. On GB200 with Ollama, I saw basically the same behavior. The main thing that moved was latency, not quality.
still benchmarking everything
Posts: 54
Threads: 3
Joined: Sep 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 quant drift.
Posts: 73
Threads: 8
Joined: Sep 2026
Reputation:
0
worth checking the driver first.
Posts: 76
Threads: 8
Joined: Aug 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. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
learning in public