Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
routing between local and hosted for Kimi
#1
I figured I'd ask here before changing everything.

I'm mostly working with Mixtral in vLLM on M3 Max. The part I'm trying to understand is NVFP4.

Not looking for the perfect answer, mostly what worked in real use.
watching release notes so you don't have to
Reply
#2
Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.
Reply
#3
Appreciate the detail. 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.
Reply
#4
I'd approach it in a boring order. On Threadripper box, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Reply
#5
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#6
Quote:What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there. Once you know the plai

Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.
Reply
#7
Quote:[quote]What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there. Once you know t

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.
curious and caffeinated
Reply
#8
Quote:[quote][quote]What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there. Once you

A couple things I'd check first. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Reply
#9
same here on my side.
Reply
#10
same here on my side.
watching release notes so you don't have to
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)