Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
flux pipeline local tips for Mixtral
#11
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at token cost.
Reply
#12
That matches what I was seeing. I ended up in about the same place using Ollama. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
small models can still be useful
Reply
#13
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.
Mostly CUDA, sometimes wrong, usually measured
Reply
#14
Maybe, but I had the opposite result. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
small models can still be good
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)