Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
what truly stays local: worth it?
#1
Did a bit of testing and thought I'd post the result here.

I tried this with Qwen using TensorRT-LLM on 5090. The headline result was better than I expected, but reranking still ended up being the limiting factor.

Nothing scientific here, just practical notes from a real setup.
Reply
#2
What worked for me was pretty simple. If you're on Ollama, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
7900 XTX / ROCm / somehow still optimistic
Reply
#3
Quote:What worked for me was pretty simple. If you're on Ollama, I'd confirm the version first and then reduce variables until the behavior is obvious. A lo

same here on my side.
Reply
#4
Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal.
Reply
#5
What worked for me was pretty simple. On A6000, 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.
7900 XTX / ROCm / somehow still optimistic
Reply
#6
Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Could be a workload difference, but I wouldn't generalize too fast from one setup.
still benchmarking everything
Reply
#7
Thanks, that helps. The pattern around token cost has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
7900 XTX / ROCm / somehow still optimistic
Reply
#8
What worked for me was pretty simple. 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.
Reply
#9
subscribed, curious where this lands.
curious and caffeinated
Reply
#10
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at long context. Once you know the plain path works, then add the faster path back in piece by piece.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)