Posts: 30
Threads: 6
Joined: Aug 2026
Reputation:
0
A couple things I'd check first. If you're on vLLM, 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: 50
Threads: 2
Joined: Sep 2026
Reputation:
0
I'd start with the simpler stack.
learning in public
Posts: 36
Threads: 2
Joined: Sep 2026
Reputation:
0
Appreciate the detail. I ended up in about the same place using MLX. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Posts: 50
Threads: 2
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. If you're on MLX, 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.
learning in public
Posts: 137
Threads: 16
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. On A6000, 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.
throughput matters, but tail latency matters too