Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MCP server discovery mess on B200
#11
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at router policy. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#12
subscribed, curious where this lands.
trying not to rebuild again
Reply
#13
Quote:subscribed, curious where this lands.

That matches what I was seeing. I ended up in about the same place using LM Studio. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
team red, team patient
Reply
#14
Did a small comparison this afternoon. 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
#15
Quote:Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly. I expected the model choice to

Need a little more detail here. What model, what runtime, and roughly what context size?
context windows are not a product strategy
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)