Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
comparing models without fooling yourself on Threadripper box
#11
Thanks, that helps. That matches what I saw on dual 3090.
post logs or it didn't happen
Reply
#12
Tried to reproduce it just now. On mini PC with Ollama, I saw basically the same behavior.
Reply
#13
Good point. That matches what I saw on Threadripper box. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.

I'm happy to test one more variant if you want a second data point.
throughput matters, but tail latency matters too
Reply
#14
Quote:Good point. That matches what I saw on Threadripper box. I got better results once I stopped chasing one metric and just looked at whether the workflo

Appreciate the detail. 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
#15
Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly.
Reply
#16
Quote:Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly.

What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at HBM constraints. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)