Posts: 35
Threads: 8
Joined: Aug 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 M3 Max.
Simple and boring is a valid answer.
My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
Posts: 48
Threads: 4
Joined: Aug 2026
Reputation:
0
I don't think that's the whole story. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Posts: 69
Threads: 3
Joined: Sep 2026
Reputation:
0
Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.
still benchmarking everything
Posts: 31
Threads: 2
Joined: Oct 2026
Reputation:
0
A couple questions before I guess too hard. Is this local-only or are you routing anything externally?
Posts: 63
Threads: 5
Joined: Sep 2026
Reputation:
0
that fixed it for me too.
Posts: 37
Threads: 5
Joined: Oct 2026
Reputation:
0
Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.
Posts: 35
Threads: 2
Joined: Aug 2026
Reputation:
0
Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.
trying not to rebuild again
