Posts: 68
Threads: 9
Joined: Sep 2026
Reputation:
0
This keeps coming up in conversation so I figured I'd start a thread.
The more I work with local setups, the more it seems like INT4 decides everything downstream.
Wondering if this is just where the whole space is heading now.
Posts: 30
Threads: 4
Joined: Sep 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.
learning in public
Posts: 39
Threads: 5
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. If you're on SGLang, 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.
Posts: 45
Threads: 4
Joined: Aug 2026
Reputation:
0
A couple questions before I guess too hard. Are you testing this on mini PC or something else?
Posts: 40
Threads: 3
Joined: Sep 2026
Reputation:
0
Quote:A couple questions before I guess too hard. Are you testing this on mini PC or something else?
Maybe, but I had the opposite result. I get why that seems right, but on 4090 the bottleneck felt elsewhere. Could be a workload difference, but I wouldn't generalize too fast from one setup.
There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Apple Silicon • MLX mostly
Posts: 36
Threads: 5
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there.
Posts: 40
Threads: 3
Joined: Sep 2026
Reputation:
0
following this because I'm in the same boat.
There are a few different conversations hiding inside this thread, so being explicit about the goal helps. At this point the real bottleneck is my patience.
Apple Silicon • MLX mostly