Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
multimodal local stack that feels real on M3 Max
#1
Wanted to compare notes with people doing similar things.

My current setup is MLX with Threadripper box, and I keep running into MoE serving.

Would appreciate practical advice rather than theory.
Reply
#2
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
small models can still be good
Reply
#3
Interesting, I hadn't tried that. The pattern around structured output 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
#4
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tokens/sec. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#5
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at MoE serving. Once you know the plain path works, then add the faster path back in piece by piece.
Reply
#6
Appreciate the detail. That matches what I saw on Threadripper box. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#7
following this because I'm in the same boat.
Reply
#8
That matches what I was seeing. That matches what I saw on GB200.
Reply
#9
Tried to reproduce it just now. On 7900 XTX with LM Studio, I saw basically the same behavior.
Reply
#10
Tried to reproduce it just now. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.
image models by night, local pipelines by day
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)