PyTorch compile got faster? on GB200

[orbitbench6]

Maybe, but I had the opposite result. I get why that seems right, but on A6000 the bottleneck felt elsewhere.

Good point. The pattern around prefill/decode split has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.

[mintstream9]

A couple things I'd check first. If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.

[tensorport]

I think the bottleneck is somewhere else. I've seen people blame workstation thermals when the real issue was much more mundane.

[dockember]

Maybe, but I had the opposite result. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model.

[cobalttinker]

A couple things I'd check first. On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.