Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
batching changes after update
#1
Thought I'd post a small recipe because a lot of threads ask similar things.

This isn't revolutionary, but the combination of PyTorch and M3 Max felt surprisingly usable once I tuned around prefill/decode split.

If someone wants the exact settings I can clean them up and post them.

For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
still benchmarking everything
Reply
#2
Ran a quick check on my box. On B200 with TensorRT-LLM, I saw basically the same behavior. I expected the model choice to matter more than it did. At this point the real bottleneck is my patience.
Reply
#3
I don't think that's the whole story. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Worth testing the simpler explanation before adopting the more interesting one.
Reply
#4
Interesting, I hadn't tried that. The pattern around workstation thermals 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.
Mostly CUDA, sometimes wrong, usually measured
Reply
#5
I don't think that's the whole story. I've seen people blame tokens/sec when the real issue was much more mundane. Worth testing the simpler explanation before adopting the more interesting one.
Reply
#6
Good point. I ended up in about the same place using SGLang. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#7
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Kimi and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
small models can still be good
Reply
#8
Appreciate the detail. I don't think your conclusion is far off.
learning in public
Reply
#9
worth checking the driver first.
Reply
#10
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)