Posts: 25
Threads: 4
Joined: Sep 2026
Reputation:
0
This keeps coming up in conversation so I figured I'd start a thread.
It feels like the conversation has shifted hard toward inference and serving details lately, and honestly that makes sense once you start dealing with KV cache pressure.
Wondering if this is just where the whole space is heading now.
My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
curious and caffeinated
Posts: 30
Threads: 0
Joined: Sep 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 KV cache pressure. Once you know the plain path works, then add the faster path back in piece by piece.
Posts: 37
Threads: 5
Joined: Oct 2026
Reputation:
0
Need a little more detail here. Do you see the same thing with a smaller batch or shorter prompt?
Posts: 49
Threads: 7
Joined: Oct 2026
Reputation:
0
Interesting, I hadn't tried that. That matches what I saw on dual 3090.
trying not to rebuild again
Posts: 29
Threads: 2
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. That matches what I saw on dual 3090.
Posts: 58
Threads: 6
Joined: Sep 2026
Reputation:
0
Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Worth testing the simpler explanation before adopting the more interesting one.
Posts: 30
Threads: 0
Joined: Sep 2026
Reputation:
0
What exact setup are you running? What model, what runtime, and roughly what context size?
Posts: 47
Threads: 4
Joined: Aug 2026
Reputation:
0
A couple questions before I guess too hard. Is this local-only or are you routing anything externally?
learning in public