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

Maybe useful as a starting point: PyTorch on Threadripper box, keeping prefix caching in mind from the start.

Maybe useful as a starting point for newer folks.

I care more about stability than squeezing the last possible tokens/sec out of it. At this point the real bottleneck is my patience.
Reply
#2
A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at consumer GPUs. Not glamorous advice, but repeatable baselines save a lot of time.
Reply
#3
That matches what I was seeing. The pattern around long context has been pretty similar for me.
learning in public
Reply
#4
I don't think that's the whole story. I've seen people blame tool calling when the real issue was much more mundane. Could be a workload difference, but I wouldn't generalize too fast from one setup.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Reply
#5
I'd start with the simpler stack.
Reply
#6
Thanks, that helps. The pattern around token cost has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#7
Quote:What worked for me was pretty simple. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lo

A couple things I'd check first. On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#8
I hit almost the same issue last night.
Reply
#9
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Phi and compare from there.
Reply
#10
Interesting, I hadn't tried that. The pattern around tool calling 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.
Apple Silicon • MLX mostly
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)