Posts: 142
Threads: 20
Joined: Sep 2026
Reputation:
0
Spent some time on this today and wanted to compare notes.
I'm comparing two approaches here: keep it simple on GB200, 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?
This is mostly for local work rather than public serving.
small models can still be useful
Posts: 29
Threads: 4
Joined: Sep 2026
Reputation:
0
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at MoE serving.
trying not to rebuild again
Posts: 73
Threads: 6
Joined: Sep 2026
Reputation:
0
Thanks, that helps. The pattern around tail latency has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Posts: 29
Threads: 6
Joined: Sep 2026
Reputation:
0
Not sure I agree there. I've seen people blame token cost when the real issue was much more mundane.
still benchmarking everything
Posts: 22
Threads: 1
Joined: Sep 2026
Reputation:
0
I think the bottleneck is somewhere else. I get why that seems right, but on mini PC the bottleneck felt elsewhere. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Posts: 40
Threads: 3
Joined: Sep 2026
Reputation:
0
Can you fill in a bit more context? Are you testing this on GB200 or something else?
If you post your exact settings, people here can probably narrow it down pretty fast.
Apple Silicon • MLX mostly
Posts: 93
Threads: 10
Joined: Oct 2026
Reputation:
0
Good point. I ended up in about the same place using Ollama. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.