Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
KV cache compression worth it for Mistral
#1
Did a bit of testing and thought I'd post the result here.

Short version: SGLang behaved well for me, but only after I stopped ignoring NVFP4.

Curious if anyone else landed in the same place.
mostly local
Reply
#2
Need a little more detail here. Is this local-only or are you routing anything externally?
Reply
#3
Good point. That matches what I saw on dual 3090. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
still benchmarking everything
Reply
#4
That matches what I was seeing. I don't think your conclusion is far off. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
curious and caffeinated
Reply
#5
Appreciate the detail. I ended up in about the same place using MLX.
Reply
#6
same here on my side.
trying not to rebuild again
Reply
#7
Quote:same here on my side.

Interesting, I hadn't tried that. The pattern around batch size has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#8
worth checking the driver first.
learning in public
Reply
#9
Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly. The main thing that moved was latency, not quality.
Reply
#10
Interesting, I hadn't tried that. I ended up in about the same place using SGLang. The biggest change for me was simplifying the stack instead of adding one more optimization layer. The logs were somehow calmer than I was.
Reply


Forum Jump:


Users browsing this thread: