Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MCP server discovery mess with vLLM
#1
Spent some time on this today and wanted to compare notes.

I'm comparing two approaches here: keep it simple on GB200, or squeeze more out of the stack and deal with the complexity.

What would you pick if you had to live with it for a few months?

This is mostly for local work rather than public serving.
small models can still be useful
Reply
#2
Quote:Spent some time on this today and wanted to compare notes.

Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Reply
#3
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at MoE serving.
trying not to rebuild again
Reply
#4
Thanks, that helps. The pattern around tail latency has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#5
Not sure I agree there. I've seen people blame token cost when the real issue was much more mundane.
still benchmarking everything
Reply
#6
Quote:Not sure I agree there. I've seen people blame token cost when the real issue was much more mundane.

What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tail latency. Not glamorous advice, but repeatable baselines save a lot of time.
Reply
#7
Quote:
Quote:Not sure I agree there. I've seen people blame token cost when the real issue was much more mundane.

I tested this tonight. My result was mixed: first run looked bad, second run looked normal. The main thing that moved was latency, not quality.
Reply
#8
I think the bottleneck is somewhere else. I get why that seems right, but on mini PC the bottleneck felt elsewhere. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Reply
#9
Can you fill in a bit more context? Are you testing this on GB200 or something else?

If you post your exact settings, people here can probably narrow it down pretty fast.
Apple Silicon • MLX mostly
Reply
#10
Good point. 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


Forum Jump:


Users browsing this thread: 1 Guest(s)