Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
benchmarks that map to real use with vLLM
#1
Did a bit of testing and thought I'd post the result here.

I tried this with Phi using vLLM on B200. The headline result was better than I expected, but continuous batching still ended up being the limiting factor.

Curious if anyone else landed in the same place.
Reply
#2
Quote:Did a bit of testing and thought I'd post the result here.

Tried to reproduce it just now. The issue went away once I changed one setting and restarted the stack cleanly. I expected the model choice to matter more than it did.
Reply
#3
same here on my side.
trying not to rebuild again
Reply
#4
Thanks, that helps. I ended up in about the same place using Ollama. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#5
Quote:Thanks, that helps. I ended up in about the same place using Ollama. Worth rechecking your defaults though, because one bad assumption can make the re

What exact setup are you running? Is this local-only or are you routing anything externally?
Reply
#6
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Phi and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#7
Good point. I ended up in about the same place using PyTorch. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#8
subscribed, curious where this lands.
Reply
#9
worth checking the driver first.
Reply
#10
that fixed it for me too.
curious and caffeinated
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)