Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
running local models on a phone
#1
Did a bit of testing and thought I'd post the result here.

Short version: llama.cpp behaved well for me, but only after I stopped ignoring KV cache pressure.

Happy to post more details if anyone wants them.
Reply
#2
worth checking the driver first. Turns out 'just one more test' was a lie.
small models can still be good
Reply
#3
that fixed it for me too.
learning in public
Reply
#4
worth checking the driver first.
trying not to rebuild again
Reply
#5
My first guess would be this: On 4090, 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.
Reply
#6
Ran a quick check on my box. On 5090 with Ollama, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput collapsed.
trying not to rebuild again
Reply
#7
following this because I'm in the same boat.
Reply
#8
My first guess would be this: If you're on TensorRT-LLM, 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.
Reply
#9
Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly.
Reply
#10
Good point. That matches what I saw on Threadripper box. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
LoRA tinkerer • dataset janitor
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)