Posts: 39
Threads: 1
Joined: Sep 2026
Reputation:
0
Posting this in case it saves someone else a little time.
I'm helping a small team set up a local workflow. We don't need a giant stack, but we do care about prefix caching.
Simple and boring is a valid answer.
This is mostly for local work rather than public serving.
queue depth watcher
Posts: 39
Threads: 1
Joined: Sep 2026
Reputation:
0
Good point. The pattern around small local stacks has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
queue depth watcher
Posts: 193
Threads: 27
Joined: Aug 2026
Reputation:
0
worth checking the driver first.
routing beats arguing over one perfect model
Posts: 32
Threads: 5
Joined: Sep 2026
Reputation:
0
Ran a quick check on my box. On 7900 XTX with Ollama, I saw basically the same behavior.
Posts: 32
Threads: 4
Joined: Aug 2026
Reputation:
0
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher. I expected the model choice to matter more than it did.
curious and caffeinated
Posts: 39
Threads: 1
Joined: Sep 2026
Reputation:
0
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
queue depth watcher
Posts: 36
Threads: 5
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.
Posts: 36
Threads: 5
Joined: Sep 2026
Reputation:
0
Thanks, that helps. I ended up in about the same place using llama.cpp.