Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
release notes that matter
#11
My first guess would be this: 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
#12
Maybe, but I had the opposite result. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Reply
#13
Appreciate the detail. I ended up in about the same place using TensorRT-LLM.
Reply
#14
Tried to reproduce it just now. 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.
routing beats arguing over one perfect model
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)