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

Two paths both seem viable, but they break down differently once prefill/decode split becomes important.

Trying to avoid rebuilding the whole thing twice.

My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
7900 XTX / ROCm / somehow still optimistic
Reply
#2
Interesting, I hadn't tried that. That matches what I saw on M3 Max.
Reply
#3
Quote:Interesting, I hadn't tried that. That matches what I saw on M3 Max.

What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#4
I tested this tonight. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.
image models by night, local pipelines by day
Reply
#5
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
7900 XTX / ROCm / somehow still optimistic
Reply
#6
Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.
Reply
#7
Thanks, that helps. That matches what I saw on mini PC. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
7900 XTX / ROCm / somehow still optimistic
Reply
#8
that fixed it for me too.
retrieval before vibes
Reply
#9
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.
small models can still be good
Reply
#10
A couple things I'd check first. On A6000, 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. The logs were somehow calmer than I was.
2x3090 • llama.cpp • too much VRAM is still not enough
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)