Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
mobile NPU reality check
#1
Spent some time on this today and wanted to compare notes.

I've gone back and forth between TensorRT-LLM and llama.cpp for Mistral. The interesting difference for me has been quant drift.

Interested in tradeoffs more than fan loyalty.
Reply
#2
I'd start with the simpler stack.
learning in public
Reply
#3
Quote:I'd start with the simpler stack.

What worked for me was pretty simple. 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.
Reply
#4
Quote:
Quote:I'd start with the simpler stack.

What worked for me was pretty simple. On 7900 XTX, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Reply
#5
Good point. 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
#6
Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.
Reply
#7
Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)