Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
router in front of vLLM for Phi
#11
subscribed, curious where this lands.
learning in public
Reply
#12
Appreciate the detail. That matches what I saw on 5090. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#13
Quote:subscribed, curious where this lands.

subscribed, curious where this lands. At this point the real bottleneck is my patience.
measure twice, benchmark three times
Reply
#14
My first guess would be this: On M3 Max, the easiest win is often to back off the aggressive settings and see whether the problem survives. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#15
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at quant drift. Not glamorous advice, but repeatable baselines save a lot of time. The logs were somehow calmer than I was.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)