Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
speculative decoding in llama.cpp
#11
Thanks, that helps. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
2x3090 • llama.cpp • too much VRAM is still not enough
Reply
#12
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. Not glamorous advice, but repeatable baselines save a lot of time.
Reply
#13
A couple questions before I guess too hard. Is this local-only or are you routing anything externally?
2x3090 • llama.cpp • too much VRAM is still not enough
Reply
#14
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#15
Quote:My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. A lot of these threads end

Good point. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#16
Quote:[quote]My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there. A lot of these threa

Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. I keep promising myself this is the last rebuild.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)