MCP server discovery mess on GB200

[promptpoint]

worth checking the driver first.

[northquill]

worth checking the driver first.

My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at batch size. Not glamorous advice, but repeatable baselines save a lot of time. Turns out 'just one more test' was a lie.

[vramarch]

That matches what I was seeing. I don't think your conclusion is far off. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.

[tensorkite]

Interesting, I hadn't tried that. I don't think your conclusion is far off.

[macrostack69]

Appreciate the detail. I ended up in about the same place using MLX. The biggest change for me was simplifying the stack instead of adding one more optimization layer.

[flintriver50]

A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Qwen and compare from there.