Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
RTX 5090 local inference for Llama
#1
Spent some time on this today and wanted to compare notes.

Two paths both seem viable, but they break down differently once token cost becomes important.

Interested in tradeoffs more than fan loyalty.

My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
Reply
#2
Quote:Spent some time on this today and wanted to compare notes.

I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at small local stacks. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#3
A couple things I'd check first. On Threadripper box, the easiest win is often to back off the aggressive settings and see whether the problem survives.
mostly local
Reply
#4
I'd approach it in a boring order. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Reply
#5
Appreciate the detail. The pattern around consumer GPUs has been pretty similar for me.
mostly local
Reply
#6
I hit almost the same issue last night.
7900 XTX / ROCm / somehow still optimistic
Reply
#7
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.
7900 XTX / ROCm / somehow still optimistic
Reply
#8
I'd approach it in a boring order. On 4090, 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.
Reply
#9
Need a little more detail here. Is this local-only or are you routing anything externally?
Reply
#10
I hit almost the same issue last night.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)