Posts: 63
Threads: 13
Joined: Sep 2026
Reputation:
0
Spent some time on this today and wanted to compare notes.
I've gone back and forth between TensorRT-LLM and vLLM for Kimi. The interesting difference for me has been KV cache pressure.
Interested in tradeoffs more than fan loyalty.
Posts: 123
Threads: 18
Joined: Sep 2026
Reputation:
0
Quote:Spent some time on this today and wanted to compare notes.
Need a little more detail here. Is this local-only or are you routing anything externally?
post logs or it didn't happen
Posts: 51
Threads: 3
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. I don't think your conclusion is far off. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Posts: 168
Threads: 14
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. Once you know the plain path works, then add the faster path back in piece by piece.
2x3090 • llama.cpp • too much VRAM is still not enough
Posts: 123
Threads: 18
Joined: Sep 2026
Reputation:
0
that fixed it for me too.
post logs or it didn't happen
Posts: 34
Threads: 6
Joined: Sep 2026
Reputation:
0
Tried to reproduce it just now. On M3 Max with SGLang, I saw basically the same behavior. The main thing that moved was latency, not quality.
Posts: 52
Threads: 6
Joined: Aug 2026
Reputation:
0
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Llama and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
Posts: 31
Threads: 6
Joined: Sep 2026
Reputation:
0
I think the bottleneck is somewhere else. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
trying not to rebuild again