Posts: 184
Threads: 23
Joined: Sep 2026
Reputation:
0
Spent some time on this today and wanted to compare notes.
Two paths both seem viable, but they break down differently once batch size becomes important.
Interested in tradeoffs more than fan loyalty.
This is mostly for local work rather than public serving.
Mostly CUDA, sometimes wrong, usually measured
Posts: 27
Threads: 1
Joined: Sep 2026
Reputation:
0
What exact setup are you running? Is this local-only or are you routing anything externally?
learning in public
Posts: 48
Threads: 8
Joined: Oct 2026
Reputation:
0
worth checking the driver first.
Posts: 199
Threads: 27
Joined: Sep 2026
Reputation:
0
Good point. I don't think your conclusion is far off.
M3 Max • MLX • local-first
Posts: 83
Threads: 6
Joined: Sep 2026
Reputation:
0
Need a little more detail here. Is this local-only or are you routing anything externally?
Posts: 70
Threads: 3
Joined: Aug 2026
Reputation:
0
Good point. I ended up in about the same place using TensorRT-LLM. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Posts: 33
Threads: 0
Joined: Aug 2026
Reputation:
0
Thanks, that helps. I ended up in about the same place using vLLM. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Posts: 37
Threads: 2
Joined: Aug 2026
Reputation:
0
Quote:Thanks, that helps. I ended up in about the same place using vLLM. I got better results once I stopped chasing one metric and just looked at whether t
Appreciate the detail. I ended up in about the same place using vLLM. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
small models can still be good
Posts: 30
Threads: 0
Joined: Sep 2026
Reputation:
0
My first guess would be this: On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time.