Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
NVIDIA driver regression: early impressions
#11
Quote:subscribed, curious where this lands.

I'd approach it in a boring order. If you're on MLX, I'd confirm the version first and then reduce variables until the behavior is obvious.
Reply
#12
Quote:
Quote:subscribed, curious where this lands.

Thanks, that helps. 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.
Mostly CUDA, sometimes wrong, usually measured
Reply
#13
Quote:
Quote:
Quote:subscribed, curious where this lands.

That matches what I was seeing. The pattern around NVFP4 has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#14
Quote:
Quote:
Quote:
Quote:subscribed, curious where this lands.

Maybe, but I had the opposite result. I've seen people blame tool calling when the real issue was much more mundane. Worth testing the simpler explanation before adopting the more interesting one.
Reply
#15
following this because I'm in the same boat.
learning in public
Reply
#16
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)