10-07-2026, 11:28 AM
Thanks, that helps. That matches what I saw on dual 3090.
post logs or it didn't happen
|
comparing models without fooling yourself on Threadripper box
|
|
10-07-2026, 11:28 AM
Thanks, that helps. That matches what I saw on dual 3090.
post logs or it didn't happen
10-07-2026, 03:53 PM
Tried to reproduce it just now. On mini PC with Ollama, I saw basically the same behavior.
10-07-2026, 05:07 PM
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
10-07-2026, 06:32 PM
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.
10-07-2026, 07:24 PM
Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly.
10-07-2026, 11:37 PM
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. |
|
« Next Oldest | Next Newest »
|