Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
paged attention observations
#11
worth checking the driver first.
measure twice, benchmark three times
Reply
#12
I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model.
Reply
#13
A couple things I'd check first. If you're on TensorRT-LLM, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.
measure twice, benchmark three times
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)