Posts: 59
Threads: 8
Joined: Sep 2026
Reputation:
0
Posting this in case it saves someone else a little time.
I'm not trying to build a perfect architecture diagram. I just want a sane starting point around MLX and A6000.
Would rather learn from your scars than collect my own all at once.
This is mostly for local work rather than public serving.
The part that surprised me was how much the boring details mattered more than the model choice.
Posts: 69
Threads: 3
Joined: Sep 2026
Reputation:
0
Quote:Posting this in case it saves someone else a little time.
A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at long context. Once you know the plain path works, then add the faster path back in piece by piece.
still benchmarking everything
Posts: 62
Threads: 4
Joined: Sep 2026
Reputation:
0
subscribed, curious where this lands.
Posts: 60
Threads: 5
Joined: Sep 2026
Reputation:
0
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.
Posts: 38
Threads: 5
Joined: Sep 2026
Reputation:
0
A couple questions before I guess too hard. What model, what runtime, and roughly what context size?
Posts: 46
Threads: 6
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. If you're on LM Studio, 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: 40
Threads: 4
Joined: Aug 2026
Reputation:
0
What worked for me was pretty simple. On 7900 XTX, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Posts: 45
Threads: 6
Joined: Sep 2026
Reputation:
0
I'd approach it in a boring order. If you're on MLX, 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: 40
Threads: 4
Joined: Aug 2026
Reputation:
0
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at token cost.
Posts: 48
Threads: 9
Joined: Sep 2026
Reputation:
0
subscribed, curious where this lands.