Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
tokens/sec tuning ideas
#1
Spent some time on this today and wanted to compare notes.

I'm comparing two approaches here: keep it simple on B200, or squeeze more out of the stack and deal with the complexity.

Interested in tradeoffs more than fan loyalty. The logs were somehow calmer than I was.
M3 Max • MLX • local-first
Reply
#2
What exact setup are you running? What model, what runtime, and roughly what context size?
Reply
#3
subscribed, curious where this lands.
Reply
#4
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
small models can still be good
Reply
#5
Maybe, but I had the opposite result. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Reply
#6
What worked for me was pretty simple. On 4090, the easiest win is often to back off the aggressive settings and see whether the problem survives. Turns out 'just one more test' was a lie.
Reply
#7
Interesting, I hadn't tried that. I don't think your conclusion is far off.
Reply
#8
Appreciate the detail. The pattern around MoE serving has been pretty similar for me.
Reply
#9
Quote:Appreciate the detail. The pattern around MoE serving has been pretty similar for me.

Did a small comparison this afternoon. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.
LoRA tinkerer • dataset janitor
Reply
#10
Good point. I don't think your conclusion is far off.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)