Posts: 63
Threads: 1
Joined: Sep 2026
Reputation:
0
Thought I'd post a small recipe because a lot of threads ask similar things.
Just sharing a setup that ended up working reasonably well: Phi, SGLang, B200, with a lot of attention on prefix caching.
Feel free to tear it apart if you see something dumb.
If I had to summarize the lesson so far, it would be that clean setup and observability beat clever guesses.
still benchmarking everything
Posts: 50
Threads: 2
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at INT4. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
learning in public
Posts: 43
Threads: 5
Joined: Sep 2026
Reputation:
0
Thanks, that helps. That matches what I saw on M3 Max. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Posts: 59
Threads: 3
Joined: Aug 2026
Reputation:
0
I think the bottleneck is somewhere else. I've seen people blame small local stacks when the real issue was much more mundane. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
Posts: 54
Threads: 7
Joined: Sep 2026
Reputation:
0
Did a small comparison this afternoon. On GB200 with SGLang, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput collapsed.
Posts: 39
Threads: 8
Joined: Aug 2026
Reputation:
0
I hit almost the same issue last night.
mostly local
Posts: 31
Threads: 6
Joined: Sep 2026
Reputation:
0
Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model.
trying not to rebuild again