Posts: 54
Threads: 3
Joined: Sep 2026
Reputation:
0
Spent some time on this today and wanted to compare notes.
I've gone back and forth between PyTorch and TensorRT-LLM for Mistral. The interesting difference for me has been speculative decoding.
Trying to avoid rebuilding the whole thing twice.
Posts: 48
Threads: 4
Joined: Aug 2026
Reputation:
0
following this because I'm in the same boat.
Posts: 341
Threads: 51
Joined: Sep 2026
Reputation:
0
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.
measure twice, benchmark three times
Posts: 47
Threads: 6
Joined: Sep 2026
Reputation:
0
That matches what I was seeing. The pattern around HBM constraints has been pretty similar for me.
Posts: 62
Threads: 5
Joined: Sep 2026
Reputation:
0
A couple questions before I guess too hard. What model, what runtime, and roughly what context size?
trying not to rebuild again
Posts: 341
Threads: 51
Joined: Sep 2026
Reputation:
0
My first guess would be this: If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time.
measure twice, benchmark three times
Posts: 40
Threads: 3
Joined: Sep 2026
Reputation:
0
Quote:My first guess would be this: If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorou
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at NVFP4. Not glamorous advice, but repeatable baselines save a lot of time.
Apple Silicon • MLX mostly
Posts: 341
Threads: 51
Joined: Sep 2026
Reputation:
0
Quote:[quote]My first guess would be this: If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious. Not g
Need a little more detail here. Do you see the same thing with a smaller batch or shorter prompt?
measure twice, benchmark three times