Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
CLI helpers for local models on 5090
#1
Did a bit of testing and thought I'd post the result here.

Short version: TensorRT-LLM behaved well for me, but only after I stopped ignoring router policy.

Happy to post more details if anyone wants them.
7900 XTX / ROCm / somehow still optimistic
Reply
#2
That matches what I was seeing. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#3
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tool calling. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.

If you post your exact settings, people here can probably narrow it down pretty fast.
learning in public
Reply
#4
Quote:My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tool calling. A lot of these

That matches what I was seeing. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#5
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. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#6
A couple things I'd check first. On 7900 XTX, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Reply
#7
Quote:A couple things I'd check first. On 7900 XTX, the easiest win is often to back off the aggressive settings and see whether the problem survives.

Maybe, but I had the opposite result. I get why that seems right, but on GB200 the bottleneck felt elsewhere.
M3 Max • MLX • local-first
Reply
#8
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. Not glamorous advice, but repeatable baselines save a lot of time.
still benchmarking everything
Reply
#9
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. Not glamorous advice, but repeatable baselines save a lot of time.
7900 XTX / ROCm / somehow still optimistic
Reply
#10
I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model.
trying not to rebuild again
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)