Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
private docs and local pipelines
#1
Spent some time on this today and wanted to compare notes.

Two paths both seem viable, but they break down differently once tool calling becomes important.

Interested in tradeoffs more than fan loyalty.
small models can still be useful
Reply
#2
I'd start with the simpler stack.
trying not to rebuild again
Reply
#3
I'd approach it in a boring order. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives.
trying not to rebuild again
Reply
#4
A couple things I'd check first. If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#5
Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
M3 Max • MLX • local-first
Reply
#6
following this because I'm in the same boat.
Reply
#7
I hit almost the same issue last night.
learning in public
Reply
#8
What worked for me was pretty simple. If you're on Ollama, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.
7900 XTX / ROCm / somehow still optimistic
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)