Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Tensor cores actually helping here
#1
worth checking the driver first.
Reply
#2
Appreciate the detail. 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.
Reply
#3
I'd approach it in a boring order. If you're on TensorRT-LLM, I'd confirm the version first and then reduce variables until the behavior is obvious.
learning in public
Reply
#4
Posting this in case it saves someone else a little time.

If you were starting from scratch today for this use case, what would you choose first and what would you ignore?

I'm especially interested in mistakes worth avoiding.

I care more about stability than squeezing the last possible tokens/sec out of it.
Reply
#5
Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?
Reply
#6
Ran a quick check on my box. 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
#7
My first guess would be this: On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Reply
#8
I hit almost the same issue last night.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)