Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
first LoRA that actually helped: early impressions
#1
Curious what people here are seeing.

I'm trying to decide whether to keep the current stack or change course. Main question is how people here are handling prefill/decode split.

Not looking for the perfect answer, mostly what worked in real use.
Reply
#2
Good point. That matches what I saw on B200. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#3
Good point. I ended up in about the same place using MLX. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
throughput matters, but tail latency matters too
Reply
#4
Good point. The pattern around MoE serving has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
throughput matters, but tail latency matters too
Reply
#5
What exact setup are you running? Is this local-only or are you routing anything externally?
small models can still be good
Reply
#6
Quote:Good point. The pattern around MoE serving has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at w

Thanks, that helps. I don't think your conclusion is far off. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)