Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
industry move that matters for local users
#1
This keeps coming up in conversation so I figured I'd start a thread.

It feels like the conversation has shifted hard toward inference and serving details lately, and honestly that makes sense once you start dealing with workstation thermals.

Curious whether that lines up with what other people are seeing.
Reply
#2
Appreciate the detail. I ended up in about the same place using PyTorch.
mostly local
Reply
#3
Maybe, but I had the opposite result. I've seen people blame batch size when the real issue was much more mundane.
watching release notes so you don't have to
Reply
#4
subscribed, curious where this lands.
learning in public
Reply
#5
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher.
still benchmarking everything
Reply
#6
That matches what I was seeing. That matches what I saw on A6000.
learning in public
Reply
#7
Appreciate the detail. That matches what I saw on A6000. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
learning in public
Reply
#8
A couple things I'd check first. On 7900 XTX, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#9
What exact setup are you running? What model, what runtime, and roughly what context size?
learning in public
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)