Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
NVIDIA driver regression: early impressions
#1
Did a bit of testing and thought I'd post the result here.

Short version: PyTorch behaved well for me, but only after I stopped ignoring token cost.

Happy to post more details if anyone wants them.

For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
Mostly CUDA, sometimes wrong, usually measured
Reply
#2
Appreciate the detail. I ended up in about the same place using PyTorch.
Reply
#3
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
still benchmarking everything
Reply
#4
Can you fill in a bit more context? Are you testing this on B200 or something else?
Reply
#5
Interesting, I hadn't tried that. That matches what I saw on 7900 XTX. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#6
Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.
Reply
#7
What worked for me was pretty simple. If you're on MLX, 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
#8
Thanks, that helps. That matches what I saw on dual 3090.
Reply
#9
Quote:Thanks, that helps. That matches what I saw on dual 3090.

Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly. The main thing that moved was latency, not quality.
Reply
#10
subscribed, curious where this lands.
mostly local
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)