Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
system prompt habits that helped on M3 Max
#11
Can you fill in a bit more context? Is this local-only or are you routing anything externally?
Reply
#12
Appreciate the detail. The pattern around prefix caching has been pretty similar for me.
Reply
#13
following this because I'm in the same boat.
Reply
#14
My first guess would be this: If you're on TensorRT-LLM, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
small models can still be useful
Reply
#15
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tokens/sec. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#16
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at continuous batching. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)