Posts: 341
Threads: 51
Joined: Sep 2026
Reputation:
0
Posting this in case it saves someone else a little time.
I'm helping a small team set up a local workflow. We don't need a giant stack, but we do care about INT4.
Simple and boring is a valid answer.
For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
measure twice, benchmark three times
Posts: 49
Threads: 6
Joined: Sep 2026
Reputation:
0
Thanks, that helps. I ended up in about the same place using MLX. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Posts: 134
Threads: 18
Joined: Sep 2026
Reputation:
0
I think the bottleneck is somewhere else. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
watching release notes so you don't have to
Posts: 15
Threads: 3
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at KV cache pressure. Once you know the plain path works, then add the faster path back in piece by piece.
Posts: 193
Threads: 27
Joined: Aug 2026
Reputation:
0
Good point. 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.
routing beats arguing over one perfect model
Posts: 73
Threads: 6
Joined: Sep 2026
Reputation:
0
Thanks, that helps. That matches what I saw on mini PC. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Posts: 59
Threads: 8
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Posts: 44
Threads: 4
Joined: Aug 2026
Reputation:
0
Appreciate the detail. I don't think your conclusion is far off.