Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
KV cache compression worth it: worth it?
#1
Has anyone else run into this?

I'm mostly working with Mistral in LM Studio on dual 3090. The part I'm trying to understand is VRAM headroom.

Would appreciate practical advice rather than theory.
team red, team patient
Reply
#2
Appreciate the detail. I ended up in about the same place using Ollama.
retrieval before vibes
Reply
#3
Maybe, but I had the opposite result. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model.
Reply
#4
What worked for me was pretty simple. If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time.
small models can still be useful
Reply
#5
What exact setup are you running? Is this local-only or are you routing anything externally? Turns out 'just one more test' was a lie.
Reply
#6
same here on my side.
Reply
#7
Need a little more detail here. What model, what runtime, and roughly what context size?
Reply
#8
That matches what I was seeing. I ended up in about the same place using LM Studio.
Reply
#9
Good point. The pattern around tokens/sec has been pretty similar for me.
Reply
#10
Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Worth testing the simpler explanation before adopting the more interesting one.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)