Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
quiet dual-GPU build advice
#1
This keeps coming up in conversation so I figured I'd start a thread.

The more I work with local setups, the more it seems like NVFP4 decides everything downstream.

Maybe obvious to some of you, but it clicked for me this week.

I care more about stability than squeezing the last possible tokens/sec out of it.
Reply
#2
Quote:This keeps coming up in conversation so I figured I'd start a thread.

worth checking the driver first.
rack in the garage • local models everywhere
Reply
#3
Quote:
Quote:This keeps coming up in conversation so I figured I'd start a thread.

Tried to reproduce it just now. My result was mixed: first run looked bad, second run looked normal.
Reply
#4
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher.
Reply
#5
Good point. That matches what I saw on 4090. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
small models can still be good
Reply
#6
Quote:Good point. That matches what I saw on 4090. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look co

I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at INT4. Not glamorous advice, but repeatable baselines save a lot of time.
Reply
#7
That matches what I was seeing. I don't think your conclusion is far off.
Reply
#8
worth checking the driver first.
Reply
#9
Can you fill in a bit more context? Are you testing this on B200 or something else?
rack in the garage • local models everywhere
Reply
#10
What worked for me was pretty simple. On M3 Max, the easiest win is often to back off the aggressive settings and see whether the problem survives.
trying not to rebuild again
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)