Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
tokens/sec tuning ideas: worth it?
#1
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: Mixtral, SGLang, A6000, with a lot of attention on consumer GPUs.

Feel free to tear it apart if you see something dumb.
Reply
#2
Did a small comparison this afternoon. On mini PC with vLLM, I saw basically the same behavior.
team red, team patient
Reply
#3
Tried to reproduce it just now. My result was mixed: first run looked bad, second run looked normal. I expected the model choice to matter more than it did.

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#4
Good point. That matches what I saw on B200. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing. The logs were somehow calmer than I was.
learning in public
Reply
#5
I hit almost the same issue last night.
Reply
#6
That matches what I was seeing. I don't think your conclusion is far off. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#7
What worked for me was pretty simple. If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious.
Reply
#8
That matches what I was seeing. That matches what I saw on GB200.
small models can still be good
Reply
#9
Quote:That matches what I was seeing. That matches what I saw on GB200.

Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.
Reply
#10
I tested this tonight. The issue went away once I changed one setting and restarted the stack cleanly. I expected the model choice to matter more than it did.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)