Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
model fallback rules that work: setup advice
#1
Thought I'd post a small recipe because a lot of threads ask similar things.

This isn't revolutionary, but the combination of Ollama and GB200 felt surprisingly usable once I tuned around router policy.

If someone wants the exact settings I can clean them up and post them.
Reply
#2
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.
still benchmarking everything
Reply
#3
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.
learning in public
Reply
#4
That matches what I was seeing. I don't think your conclusion is far off. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#5
I think the bottleneck is somewhere else. I've seen people blame small local stacks when the real issue was much more mundane.
Reply
#6
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Mixtral and compare from there.
Reply
#7
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there.
Reply
#8
A couple things I'd check first. On mini PC, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time.
Reply
#9
That matches what I was seeing. I don't think your conclusion is far off. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#10
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)