Posts: 41
Threads: 7
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.
Would rather learn from your scars than collect my own all at once.
curious and caffeinated
Posts: 24
Threads: 2
Joined: Aug 2026
Reputation:
0
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.
Posts: 65
Threads: 5
Joined: Sep 2026
Reputation:
0
I hit almost the same issue last night.
Posts: 45
Threads: 4
Joined: Aug 2026
Reputation:
0
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
Posts: 70
Threads: 3
Joined: Aug 2026
Reputation:
0
Need a little more detail here. Is this local-only or are you routing anything externally?
Posts: 17
Threads: 1
Joined: Sep 2026
Reputation:
0
I think the bottleneck is somewhere else. I get why that seems right, but on Threadripper box the bottleneck felt elsewhere. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
Posts: 62
Threads: 6
Joined: Sep 2026
Reputation:
0
Did a small comparison this afternoon. On A6000 with SGLang, I saw basically the same behavior.
Posts: 199
Threads: 27
Joined: Sep 2026
Reputation:
0
My first guess would be this: On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives. Turns out 'just one more test' was a lie.
M3 Max • MLX • local-first