Posts: 73
Threads: 6
Joined: Sep 2026
Reputation:
0
Thought I'd post a small recipe because a lot of threads ask similar things.
This isn't revolutionary, but the combination of llama.cpp and 7900 XTX felt surprisingly usable once I tuned around prefill/decode split.
Maybe useful as a starting point for newer folks.
Posts: 63
Threads: 7
Joined: Sep 2026
Reputation:
0
Thanks, that helps. I ended up in about the same place using llama.cpp. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Posts: 60
Threads: 9
Joined: Aug 2026
Reputation:
0
A couple things I'd check first. On M3 Max, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Posts: 56
Threads: 7
Joined: Sep 2026
Reputation:
0
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. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Posts: 43
Threads: 3
Joined: Sep 2026
Reputation:
0
subscribed, curious where this lands.
There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
mostly local
Posts: 55
Threads: 8
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 tool calling. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Apple Silicon • MLX mostly
Posts: 80
Threads: 11
Joined: Aug 2026
Reputation:
0
Interesting, I hadn't tried that. The pattern around structured output has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Posts: 53
Threads: 4
Joined: Sep 2026
Reputation:
0
subscribed, curious where this lands.