Posts: 31
Threads: 5
Joined: Sep 2026
Reputation:
0
Quote:Appreciate the detail. I don't think your conclusion is far off.
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at quant drift.
small models can still be good
Posts: 54
Threads: 3
Joined: Sep 2026
Reputation:
0
Appreciate the detail. I don't think your conclusion is far off.
Posts: 33
Threads: 0
Joined: Aug 2026
Reputation:
0
Interesting, I hadn't tried that. I ended up in about the same place using PyTorch. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
If you post your exact settings, people here can probably narrow it down pretty fast.
Posts: 34
Threads: 5
Joined: Aug 2026
Reputation:
0
I tested this tonight. The issue went away once I changed one setting and restarted the stack cleanly. The main thing that moved was latency, not quality.
I'm happy to test one more variant if you want a second data point.
Posts: 41
Threads: 0
Joined: Oct 2026
Reputation:
0
Interesting, I hadn't tried that. I ended up in about the same place using vLLM.
Posts: 37
Threads: 4
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
If you post your exact settings, people here can probably narrow it down pretty fast.
Posts: 52
Threads: 5
Joined: Aug 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 PyTorch and 7900 XTX felt surprisingly usable once I tuned around continuous batching.
Maybe useful as a starting point for newer folks.
I care more about stability than squeezing the last possible tokens/sec out of it.
trying not to rebuild again