Posts: 50
Threads: 4
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 HBM constraints decides everything downstream.
Maybe obvious to some of you, but it clicked for me this week.
Posts: 184
Threads: 23
Joined: Sep 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. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
Mostly CUDA, sometimes wrong, usually measured
Posts: 80
Threads: 11
Joined: Aug 2026
Reputation:
0
A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at consumer GPUs. Not glamorous advice, but repeatable baselines save a lot of time.
Posts: 30
Threads: 4
Joined: Sep 2026
Reputation:
0
My first guess would be this: On M3 Max, 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.
learning in public
Posts: 33
Threads: 5
Joined: Aug 2026
Reputation:
0
Need a little more detail here. Is this local-only or are you routing anything externally?
Posts: 184
Threads: 23
Joined: Sep 2026
Reputation:
0
Quote:Need a little more detail here. Is this local-only or are you routing anything externally?
I'd approach it in a boring order. If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time.
Mostly CUDA, sometimes wrong, usually measured
Posts: 54
Threads: 7
Joined: Sep 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. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Posts: 32
Threads: 1
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. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Posts: 73
Threads: 6
Joined: Sep 2026
Reputation:
0
Good point. The pattern around embeddings has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Posts: 184
Threads: 23
Joined: Sep 2026
Reputation:
0
Appreciate the detail. The pattern around tool calling has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Mostly CUDA, sometimes wrong, usually measured