Posts: 17
Threads: 4
Joined: Sep 2026
Reputation:
0
Did a bit of testing and thought I'd post the result here.
Short version: PyTorch behaved well for me, but only after I stopped ignoring NVFP4.
Happy to post more details if anyone wants them.
curious and caffeinated
Posts: 193
Threads: 27
Joined: Aug 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. Could be a workload difference, but I wouldn't generalize too fast from one setup.
routing beats arguing over one perfect model
Posts: 27
Threads: 1
Joined: Aug 2026
Reputation:
0
My first guess would be this: If you're on MLX, I'd confirm the version first and then reduce variables until the behavior is obvious.
Posts: 193
Threads: 27
Joined: Aug 2026
Reputation:
0
subscribed, curious where this lands.
routing beats arguing over one perfect model
Posts: 37
Threads: 2
Joined: Aug 2026
Reputation:
0
I'd approach it in a boring order. If you're on vLLM, 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.
small models can still be good
Posts: 31
Threads: 2
Joined: Oct 2026
Reputation:
0
Need a little more detail here. What model, what runtime, and roughly what context size?
Posts: 193
Threads: 27
Joined: Aug 2026
Reputation:
0
following this because I'm in the same boat.
routing beats arguing over one perfect model
Posts: 22
Threads: 1
Joined: Sep 2026
Reputation:
0
Did a small comparison this afternoon. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.