Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
privacy wins of local models: setup advice
#1
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.
Reply
#2
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
Reply
#3
I tested this tonight. My result was mixed: first run looked bad, second run looked normal.
Reply
#4
Good point. I ended up in about the same place using PyTorch.
M3 Max • MLX • local-first
Reply
#5
Good point. The pattern around reranking has been pretty similar for me.
Reply
#6
following this because I'm in the same boat. The logs were somehow calmer than I was.
Reply
#7
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.
Reply
#8
Can you fill in a bit more context? Is this local-only or are you routing anything externally?
mostly local
Reply
#9
I'd start with the simpler stack.
Reply
#10
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
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)