Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
synthetic data for support bots on 7900 XTX
#11
Quote:[quote][quote]I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and n

Thanks, that helps. The pattern around batch size has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.

I'm happy to test one more variant if you want a second data point.
Reply
#12
that fixed it for me too.
Reply
#13
Not sure I agree there. I get why that seems right, but on A6000 the bottleneck felt elsewhere. Worth testing the simpler explanation before adopting the more interesting one. Turns out 'just one more test' was a lie.
routing beats arguing over one perfect model
Reply
#14
Quote:Not sure I agree there. I get why that seems right, but on A6000 the bottleneck felt elsewhere. Worth testing the simpler explanation before adopting

Thanks, that helps. The pattern around continuous batching has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
serving stack tinkerer
Reply
#15
Quote:I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model.

Not sure I agree there. I get why that seems right, but on 7900 XTX the bottleneck felt elsewhere. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Reply
#16
Quote:[quote]I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the

A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there.
small models can still be good
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)