Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
router in front of vLLM for Phi
#1
Curious what people here are seeing.

My current setup is LM Studio with B200, and I keep running into MoE serving.

Not looking for the perfect answer, mostly what worked in real use.

For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
measure twice, benchmark three times
Reply
#2
worth checking the driver first.
Reply
#3
Did a small comparison this afternoon. I couldn't reproduce the slowdown until I pushed context much higher. I expected the model choice to matter more than it did.
Reply
#4
I'd start with the simpler stack.
serving stack tinkerer
Reply
#5
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
throughput matters, but tail latency matters too
Reply
#6
Quote:What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there. Once you know the p

following this because I'm in the same boat.
Reply
#7
that fixed it for me too.
Reply
#8
A couple things I'd check first. On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Reply
#9
What exact setup are you running? Is this local-only or are you routing anything externally?
serving stack tinkerer
Reply
#10
Good point. The pattern around quant drift 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.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)