Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
when a plain Python stack is enough for FLUX
#11
Quote:that fixed it for me too. The logs were somehow calmer than I was.

Thanks, that helps. That matches what I saw on M3 Max.
learning in public
Reply
#12
A couple questions before I guess too hard. Is this local-only or are you routing anything externally?
Reply
#13
Ran a quick check on my box. On 7900 XTX with llama.cpp, I saw basically the same behavior. The main thing that moved was latency, not quality.
Reply
#14
Not sure I agree there. I've seen people blame consumer GPUs when the real issue was much more mundane. Worth testing the simpler explanation before adopting the more interesting one.
queue depth watcher
Reply
#15
Quote:I think the bottleneck is somewhere else. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.

Can you fill in a bit more context? Are you testing this on dual 3090 or something else?
measure twice, benchmark three times
Reply
#16
Appreciate the detail. I don't think your conclusion is far off.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)