Posts: 45
Threads: 4
Joined: Aug 2026
Reputation:
0
Thought I'd post a small recipe because a lot of threads ask similar things.
Just sharing a setup that ended up working reasonably well: Gemma, TensorRT-LLM, A6000, with a lot of attention on tool calling.
Maybe useful as a starting point for newer folks.
Posts: 36
Threads: 5
Joined: Sep 2026
Reputation:
0
I'd start with the simpler stack.
Posts: 37
Threads: 4
Joined: Sep 2026
Reputation:
0
Appreciate the detail. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
I'm happy to test one more variant if you want a second data point.
Posts: 41
Threads: 4
Joined: Sep 2026
Reputation:
0
I'd start with the simpler stack.
Posts: 68
Threads: 9
Joined: Sep 2026
Reputation:
0
My first guess would be this: If you're on Ollama, I'd confirm the version first and then reduce variables until the behavior is obvious.
Posts: 53
Threads: 5
Joined: Sep 2026
Reputation:
0
I'd approach it in a boring order. On Threadripper box, 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.
small models can still be good
Posts: 31
Threads: 2
Joined: Sep 2026
Reputation:
0
Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher.
Posts: 193
Threads: 27
Joined: Aug 2026
Reputation:
0
Need a little more detail here. Is this local-only or are you routing anything externally?
routing beats arguing over one perfect model
Posts: 68
Threads: 9
Joined: Sep 2026
Reputation:
0
My first guess would be this: If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious.