Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
human evals on small teams for Phi
#1
I tested this tonight. The issue went away once I changed one setting and restarted the stack cleanly.
Reply
#2
A couple things I'd check first. On mini PC, the easiest win is often to back off the aggressive settings and see whether the problem survives.
Reply
#3
worth checking the driver first.
Reply
#4
that fixed it for me too.
queue depth watcher
Reply
#5
Quote:Can you fill in a bit more context? Are you testing this on 7900 XTX or something else?

A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Qwen and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#6
subscribed, curious where this lands. I keep promising myself this is the last rebuild.
2x3090 • llama.cpp • too much VRAM is still not enough
Reply
#7
Not sure I agree there. I've seen people blame speculative decoding 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.
7900 XTX / ROCm / somehow still optimistic
Reply
#8
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 continuous batching decides everything downstream.

Maybe obvious to some of you, but it clicked for me this week.
Reply
#9
Appreciate the detail. That matches what I saw on 5090. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
queue depth watcher
Reply
#10
Good point. I ended up in about the same place using LM Studio. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)