Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
best local open-weight model this week
#1
This keeps coming up in conversation so I figured I'd start a thread.

The more I work with local setups, the more it seems like tail latency decides everything downstream.

Curious whether that lines up with what other people are seeing.
Reply
#2
What exact setup are you running? Is this local-only or are you routing anything externally?
post logs or it didn't happen
Reply
#3
Quote:What exact setup are you running? Is this local-only or are you routing anything externally?

Appreciate the detail. I don't think your conclusion is far off. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#4
Ran a quick check on my box. On 7900 XTX with PyTorch, I saw basically the same behavior.
Reply
#5
I'd start with the simpler stack.
Reply
#6
I hit almost the same issue last night.
learning in public
Reply
#7
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tail latency.
Reply
#8
I'd start with the simpler stack.
Reply
#9
Appreciate the detail. I don't think your conclusion is far off.
Reply
#10
What worked for me was pretty simple. Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)