Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
when video is still not worth the wait
#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 token cost decides everything downstream.

Curious whether that lines up with what other people are seeing.

This is mostly for local work rather than public serving.
Reply
#2
Thanks, that helps. That matches what I saw on A6000. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#3
that fixed it for me too.
Reply
#4
Thanks, that helps. I don't think your conclusion is far off.
trying not to rebuild again
Reply
#5
That matches what I was seeing. The pattern around long context has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#6
following this because I'm in the same boat.

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#7
Maybe, but I had the opposite result. I get why that seems right, but on B200 the bottleneck felt elsewhere. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Reply
#8
A couple questions before I guess too hard. Are you testing this on M3 Max or something else?
Reply
#9
Quote:A couple questions before I guess too hard. Are you testing this on M3 Max or something else?

Appreciate the detail. I ended up in about the same place using PyTorch. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
small models can still be useful
Reply
#10
Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal. I expected the model choice to matter more than it did.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)