Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Best workstation layout for local models
#1
Spent some time on this today and wanted to compare notes.

Two paths both seem viable, but they break down differently once tokens/sec becomes important.

Trying to avoid rebuilding the whole thing twice.

I care more about stability than squeezing the last possible tokens/sec out of it.
learning in public
Reply
#2
Quote:Spent some time on this today and wanted to compare notes.

I'd approach it in a boring order. On 7900 XTX, 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.
rack in the garage • local models everywhere
Reply
#3
Ran a quick check on my box. On Threadripper box with llama.cpp, I saw basically the same behavior. The main thing that moved was latency, not quality.
Reply
#4
Appreciate the detail. I ended up in about the same place using LM Studio.
Reply
#5
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
#6
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at NVFP4. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#7
Can you fill in a bit more context? Is this local-only or are you routing anything externally?
Reply
#8
Need a little more detail here. Do you see the same thing with a smaller batch or shorter prompt?
M3 Max • MLX • local-first
Reply
#9
Not sure I agree there. I get why that seems right, but on 7900 XTX the bottleneck felt elsewhere. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)