Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
best local runtime for mixed models
#1
Spent some time on this today and wanted to compare notes.

Two paths both seem viable, but they break down differently once continuous batching becomes important.

Trying to avoid rebuilding the whole thing twice.
Reply
#2
A couple questions before I guess too hard. Are you testing this on 5090 or something else?
learning in public
Reply
#3
Interesting, I hadn't tried that. The pattern around token cost has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#4
Appreciate the detail. The pattern around tokens/sec has been pretty similar for me.
Reply
#5
I'd start with the simpler stack.
curious and caffeinated
Reply
#6
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.
Reply
#7
Maybe, but I had the opposite result. I've seen people blame HBM constraints when the real issue was much more mundane.
trying not to rebuild again
Reply
#8
Did a small comparison this afternoon. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.
2x3090 • llama.cpp • too much VRAM is still not enough
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)