Posts: 36
Threads: 5
Joined: Sep 2026
Reputation:
0
Spent some time on this today and wanted to compare notes.
I'm comparing two approaches here: keep it simple on A6000, or squeeze more out of the stack and deal with the complexity.
Interested in tradeoffs more than fan loyalty.
Posts: 37
Threads: 4
Joined: Sep 2026
Reputation:
0
Did a small comparison this afternoon. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.
If you post your exact settings, people here can probably narrow it down pretty fast.
Posts: 40
Threads: 3
Joined: Sep 2026
Reputation:
0
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.
Apple Silicon • MLX mostly
Posts: 134
Threads: 18
Joined: Sep 2026
Reputation:
0
Tried to reproduce it just now. My result was mixed: first run looked bad, second run looked normal.
watching release notes so you don't have to
Posts: 199
Threads: 27
Joined: Sep 2026
Reputation:
0
Appreciate the detail. I don't think your conclusion is far off.
M3 Max • MLX • local-first
Posts: 40
Threads: 4
Joined: Sep 2026
Reputation:
0
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at workstation thermals. Once you know the plain path works, then add the faster path back in piece by piece.