Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
70B still worth the pain
#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 structured output decides everything downstream.

Maybe obvious to some of you, but it clicked for me this week.
Reply
#2
Ran a quick check on my box. On 7900 XTX with SGLang, I saw basically the same behavior. The main thing that moved was latency, not quality.
small models can still be good
Reply
#3
That matches what I was seeing. That matches what I saw on B200. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#4
Good point. 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
#5
Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet. At this point the real bottleneck is my patience.
Reply
#6
A couple questions before I guess too hard. Are you testing this on B200 or something else?

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#7
Quote:A couple questions before I guess too hard. Are you testing this on B200 or something else?

Good point. That matches what I saw on dual 3090. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
measure twice, benchmark three times
Reply
#8
Quote:
Quote:A couple questions before I guess too hard. Are you testing this on B200 or something else?

Good point. That matches what I saw on 7900 XTX.
Reply
#9
I'd start with the simpler stack.
Reply
#10
Quote:I'd start with the simpler stack.

that fixed it for me too.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)