Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
NVIDIA driver regression
#1
Thought I'd post a small recipe because a lot of threads ask similar things.

Maybe useful as a starting point: TensorRT-LLM on 7900 XTX, keeping HBM constraints in mind from the start.

If someone wants the exact settings I can clean them up and post them.
Reply
#2
That matches what I was seeing. The pattern around token cost has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#3
Quote:That matches what I was seeing. The pattern around token cost has been pretty similar for me. The biggest change for me was simplifying the stack inst

I don't think that's the whole story. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Mostly CUDA, sometimes wrong, usually measured
Reply
#4
Quote:[quote]That matches what I was seeing. The pattern around token cost has been pretty similar for me. The biggest change for me was simplifying the sta

That matches what I was seeing. I don't think your conclusion is far off.
Reply
#5
Can you fill in a bit more context? Are you testing this on B200 or something else?
Reply
#6
Quote:Can you fill in a bit more context? Are you testing this on B200 or something else?

Need a little more detail here. Are you testing this on 4090 or something else?
learning in public
Reply
#7
Quote:
Quote:Can you fill in a bit more context? Are you testing this on B200 or something else?

What worked for me was pretty simple. On Threadripper box, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Reply
#8
Quote:
Quote:
Quote:Can you fill in a bit more context? Are you testing this on B200 or something else?

My first guess would be this: Before rebuilding anything, I'd test one clean baseline with DeepSeek and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
Reply
#9
Quote:
Quote:
Quote:
Quote:Can you fill in a bit more context? Are you testing this on B200 or something else?

That matches what I was seeing. That matches what I saw on Threadripper box. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#10
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with FLUX and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)