Posts: 49
Threads: 9
Joined: Aug 2026
Reputation:
0
Thought I'd post a small recipe because a lot of threads ask similar things.
Just sharing a setup that ended up working reasonably well: Mixtral, MLX, B200, with a lot of attention on token cost.
Maybe useful as a starting point for newer folks.
For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day. Turns out 'just one more test' was a lie.
Posts: 28
Threads: 6
Joined: Aug 2026
Reputation:
0
My first guess would be this: If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time.
Posts: 134
Threads: 18
Joined: Sep 2026
Reputation:
0
Good point. The pattern around reranking has been pretty similar for me.
watching release notes so you don't have to
Posts: 49
Threads: 6
Joined: Sep 2026
Reputation:
0
worth checking the driver first.
Posts: 48
Threads: 9
Joined: Sep 2026
Reputation:
0
Need a little more detail here. Is this local-only or are you routing anything externally?
Posts: 53
Threads: 3
Joined: Aug 2026
Reputation:
0
Appreciate the detail. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Posts: 49
Threads: 9
Joined: Aug 2026
Reputation:
0
subscribed, curious where this lands.
Posts: 47
Threads: 6
Joined: Sep 2026
Reputation:
0
That matches what I was seeing. That matches what I saw on B200. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Posts: 38
Threads: 4
Joined: Aug 2026
Reputation:
0
subscribed, curious where this lands.
curious and caffeinated