Posts: 26
Threads: 3
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 llama.cpp and Threadripper box.
I'm especially interested in mistakes worth avoiding.
I care more about stability than squeezing the last possible tokens/sec out of it.
Posts: 40
Threads: 3
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Apple Silicon • MLX mostly
Posts: 31
Threads: 5
Joined: Sep 2026
Reputation:
0
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher.
small models can still be good
Posts: 62
Threads: 4
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: 45
Threads: 2
Joined: Aug 2026
Reputation:
0
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Llama and compare from there.
Posts: 44
Threads: 0
Joined: Sep 2026
Reputation:
0
That matches what I was seeing. That matches what I saw on GB200. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
still benchmarking everything
Posts: 24
Threads: 1
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.
small models can still be good