Posts: 66
Threads: 7
Joined: Sep 2026
Reputation:
0
Has anyone else run into this?
I'm mostly working with Kimi in llama.cpp on A6000. The part I'm trying to understand is INT4.
Would appreciate practical advice rather than theory.
My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
Posts: 211
Threads: 21
Joined: Sep 2026
Reputation:
0
A couple things I'd check first. If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious. Once you know the plain path works, then add the faster path back in piece by piece.
7900 XTX / ROCm / somehow still optimistic
Posts: 40
Threads: 8
Joined: Sep 2026
Reputation:
0
I tested this tonight. My result was mixed: first run looked bad, second run looked normal.
Posts: 199
Threads: 27
Joined: Sep 2026
Reputation:
0
Good point. I ended up in about the same place using PyTorch.
M3 Max • MLX • local-first
Posts: 65
Threads: 5
Joined: Sep 2026
Reputation:
0
Good point. The pattern around reranking has been pretty similar for me.
Posts: 54
Threads: 3
Joined: Sep 2026
Reputation:
0
following this because I'm in the same boat. The logs were somehow calmer than I was.
Posts: 63
Threads: 4
Joined: Sep 2026
Reputation:
0
I don't think that's the whole story. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
Posts: 30
Threads: 0
Joined: Sep 2026
Reputation:
0
Can you fill in a bit more context? Is this local-only or are you routing anything externally?
mostly local
Posts: 82
Threads: 7
Joined: Sep 2026
Reputation:
0
I'd start with the simpler stack.
Posts: 63
Threads: 1
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. That matches what I saw on B200. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
still benchmarking everything